Triple
T32330016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Lathom |
E826023
|
entity |
| Predicate | notableOfficeHeldByTitleholder |
P5750
|
FINISHED |
| Object | Lord Chamberlain |
E42500
|
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: Lord Chamberlain | Statement: [Earl of Lathom, notableOfficeHeldByTitleholder, Lord Chamberlain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOfficeHeldByTitleholder Context triple: [Earl of Lathom, notableOfficeHeldByTitleholder, Lord Chamberlain]
-
A.
notableTitleHeld
Indicates that an entity has held a distinguished or noteworthy title, rank, or official position.
-
B.
notableFormerOfficeHolderRole
Indicates that an entity previously held a particular official position or role that is considered notable.
-
C.
notableOfficeHolder
chosen
Indicates that an entity is a significant or distinguished holder of a particular office or position associated with another entity.
-
D.
notableHolderOccupation
Indicates that a person notably associated with an entity (e.g., an award, office, or title) held a particular occupation or professional role.
-
E.
notableOfficePeriod
Indicates that an entity held a particular office or position during a specified time period.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3057242d6081909be790ac6516706e |
completed | June 15, 2026, 7:48 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:47 a.m.