Triple
T3467096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Lieutenant of Ireland |
E73162
|
entity |
| Predicate | wasUsuallyHeldByRank |
P7007
|
FINISHED |
| Object | earl |
—
|
LITERAL 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: earl | Statement: [Lord Lieutenant of Ireland, wasUsuallyHeldByRank, earl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasUsuallyHeldByRank Context triple: [Lord Lieutenant of Ireland, wasUsuallyHeldByRank, earl]
-
A.
formerRanking
Indicates that an entity previously held a particular rank or position but no longer does so.
-
B.
typicallyHoldsRank
chosen
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
-
C.
rankAtOpening
Indicates the position or level an entity holds within an ordered ranking at the initial or starting point of a specified period or event.
-
D.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
E.
seniorRank
Indicates that one entity holds a higher or more senior rank or position than another entity.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb1090188190ac8aafd87dfaa6a7 |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.