Triple
T38011553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bentley family |
E948376
|
entity |
| Predicate | operatedImprint |
P53838
|
FINISHED |
| Object | Bentley’s Miscellany |
E281187
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Bentley’s Miscellany | Statement: [Bentley family, operatedImprint, Bentley’s Miscellany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedImprint Context triple: [Bentley family, operatedImprint, Bentley’s Miscellany]
-
A.
distributorImprint
Indicates that one entity serves as the distributing imprint or label responsible for releasing or circulating another entity (such as a work or product).
-
B.
overseesImprint
Indicates that one entity has managerial or supervisory responsibility over the operations or activities of another entity, typically a subsidiary brand or imprint.
-
C.
publisherImprint
Indicates the publishing imprint or brand under which a work is issued by a publisher.
-
D.
operatedPublication
chosen
Indicates that one entity manages, runs, or oversees the functioning of a particular publication.
-
E.
publisherImprintOwner
Indicates that one entity is the owning or parent organization responsible for the publisher imprint of another entity.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0340784c488190aa6c7c9be2e8a434 |
completed | May 12, 2026, 3 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4154358d4481909d6e47fbc43f0c24 |
completed | June 28, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_6a033f33eddc819091507716f6ed7d7d |
completed | May 12, 2026, 2:54 p.m. |
Created at: May 3, 2026, 4:20 p.m.