Triple
T37811811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess of Mar |
E942665
|
entity |
| Predicate | titleHolderMaySitIn |
P98388
|
FINISHED |
| Object | House of Lords (historically) |
—
|
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: House of Lords (historically) | Statement: [Countess of Mar, titleHolderMaySitIn, House of Lords (historically)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderMaySitIn Context triple: [Countess of Mar, titleHolderMaySitIn, House of Lords (historically)]
-
A.
titleHolderDoesNotSitByRight
Indicates that the person holding the title is not seated immediately to the right of the referenced person or position.
-
B.
titleHolderSatIn
chosen
Indicates that the title holder occupied a seat or position in a specified place or context.
-
C.
titleHolderCouldBe
Indicates that a particular entity is a possible or potential holder of a specified title or position.
-
D.
titleHolderQualifiedFor
Indicates that the current holder of a title meets the necessary conditions or criteria to be eligible for that title.
-
E.
titleHolderWas
Indicates that an entity previously held a specific title or position before it passed to someone or something else.
- 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00053d8004819097ad9cf6431a20a3 |
completed | May 10, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_6a0004b3a82c81908e2bf9a533a93eb6 |
completed | May 10, 2026, 4:08 a.m. |
Created at: May 3, 2026, 4:19 p.m.