Triple
T26265727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Stanley, 4th Earl of Derby |
E656975
|
entity |
| Predicate | heldCourtOffice |
P11962
|
FINISHED |
| Object | Lord High Steward |
—
|
NE NERFINISHED |
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 High Steward | Statement: [Henry Stanley, 4th Earl of Derby, heldCourtOffice, Lord High Steward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldCourtOffice Context triple: [Henry Stanley, 4th Earl of Derby, heldCourtOffice, Lord High Steward]
-
A.
heldCourtUnder
Indicates that one authority conducted judicial or ceremonial court proceedings under the jurisdiction, auspices, or authority of another.
-
B.
heldCourtIn
Indicates that an authority or governing body formally conducted judicial or official proceedings in a particular place.
-
C.
heldJudicialPositionIn
chosen
Indicates that an entity served in an official judicial role or office within a specified jurisdiction or court.
-
D.
heldByCourt
Indicates that a particular legal position, opinion, or decision is asserted or determined by a court.
-
E.
hostCourtOf
Indicates that one entity serves as the venue or location where the court associated with another entity is held or convened.
- F. None of above.
Provenance (3 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60e047d0081909bbc4d4324d93578 |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:11 p.m.