Triple
T30971271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander family, Earls of Caledon |
E789103
|
entity |
| Predicate | hasEarlierTitle |
P155834
|
FINISHED |
| Object | Viscount Caledon |
—
|
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: Viscount Caledon | Statement: [Alexander family, Earls of Caledon, hasEarlierTitle, Viscount Caledon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarlierTitle Context triple: [Alexander family, Earls of Caledon, hasEarlierTitle, Viscount Caledon]
-
A.
hasLaterTitle
Indicates that one title occurs chronologically after another title in a sequence or timeline.
-
B.
hasFormerTitle
chosen
Indicates that an entity previously held a specific title or position but no longer does.
-
C.
hasTitleSince
Indicates that an entity has held a particular title continuously starting from a specified point in time.
-
D.
replacedEarlierTitle
Indicates that one title or designation has been superseded by an earlier title that it replaced in a sequence of naming or labeling.
-
E.
hadTitle
Indicates that an entity held or was assigned a specific title or formal designation.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:54 p.m.