Triple
T14807476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Beatty |
E348074
|
entity |
| Predicate | firstHolderLifespan |
P115805
|
FINISHED |
| Object | 1871–1936 |
—
|
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: 1871–1936 | Statement: [Baron Beatty, firstHolderLifespan, 1871–1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHolderLifespan Context triple: [Baron Beatty, firstHolderLifespan, 1871–1936]
-
A.
firstHeldFor
Indicates the initial time period or event during which an entity was first held, possessed, or hosted by another entity.
-
B.
firstHolderDate
Indicates the date on which an entity first became the holder or owner of another entity (e.g., an asset, title, or right).
-
C.
firstHolderEnd
Indicates that the specified entity is the one who initially held something and that this holding relationship has come to an end.
-
D.
firstHeldAs
Indicates the initial time or context in which an entity was first possessed, owned, or held by another entity.
-
E.
firstHeldAt
Indicates the initial time or event at which an entity was first held, possessed, or hosted.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decf33b6a08190ab6a4cfeda2cc09c |
completed | April 14, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:42 a.m.