Triple
T11842091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Battle of the Ages |
E281675
|
entity |
| Predicate | linealTitleAtStake |
P5850
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Battle of the Ages, linealTitleAtStake, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linealTitleAtStake Context triple: [The Battle of the Ages, linealTitleAtStake, yes]
-
A.
titleOnTheLine
Indicates that a title or heading is positioned directly on a specific line (such as a line of text, a boundary, or a graphical line) rather than above, below, or separate from it.
-
B.
titleContested
chosen
Indicates that the legitimacy or ownership of a title is disputed between parties.
-
C.
claimedTitle
Indicates that an entity asserts or declares possession of a particular title or rank.
-
D.
aimedTitle
Indicates that one entity is the intended or targeted title or heading associated with another entity.
-
E.
title
Indicates that one entity serves as the formal name or designation of 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.