Triple
T22095352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Clinton |
E546012
|
entity |
| Predicate | isAmongOldestBaronies |
P146972
|
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, isAmongOldestBaronies, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAmongOldestBaronies Context triple: [Baron Clinton, isAmongOldestBaronies, true]
-
A.
hasNumberOfCompanionBaronies
Indicates the specific count of companion baronies associated with a given entity.
-
B.
isOldestRankOfKnighthoodIn
Indicates that a particular rank of knighthood is the most senior or highest-ranking within a specified order, system, or jurisdiction.
-
C.
hasNotableBarony
Indicates that an entity possesses or is associated with a barony that is considered notable or significant in some context.
-
D.
historicBarony
Indicates that an entity has the status or role of a historic barony, i.e., it was once recognized as a baronial territorial or feudal jurisdiction.
-
E.
companionBarony
Indicates a relationship where one barony is designated as an accompanying or associated barony to another, typically linked or paired in status or function.
- F. None of above. chosen
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_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. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:29 p.m.