Triple
T22095329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Clinton |
E546012
|
entity |
| Predicate | isAncientTitle |
P136285
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Baron Clinton, isAncientTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAncientTitle Context triple: [Baron Clinton, isAncientTitle, true]
-
A.
ancientTitle
chosen
Indicates that an entity holds or is associated with a title or designation originating from ancient times.
-
B.
isAncient
Indicates that the entity existed or originated in a very distant past, typically far earlier than the commonly referenced historical period.
-
C.
isHistoricTitle
Indicates that a given title or designation was used in the past and is no longer current, but is retained for historical reference.
-
D.
isMilitaryEraTitleFor
Indicates that one title is the official or recognized designation used for a person, unit, or role during a specific military era or period.
-
E.
hasAncestralTitle
Indicates that an entity holds or is associated with a hereditary or historically inherited title passed down through ancestry.
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e82c1481908701f255b834f192 |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.