Triple
T14707065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War of the Five Kings |
E345453
|
entity |
| Predicate | startsInFictionalYear |
P16819
|
FINISHED |
| Object | 298 AC |
—
|
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: 298 AC | Statement: [War of the Five Kings, startsInFictionalYear, 298 AC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startsInFictionalYear Context triple: [War of the Five Kings, startsInFictionalYear, 298 AC]
-
A.
activeInFictionalYear
Indicates that an entity is active or operating during a specified fictional or imaginary year within a narrative or fictional timeline.
-
B.
foundedInFictionalYear
chosen
Indicates that an entity was established or created in a year that exists only within a fictional or imaginary timeline, rather than in real-world history.
-
C.
fictionalBirthYear
Indicates the year in which a fictional character is stated or assumed to have been born within its narrative or canon.
-
D.
endedInYear
Indicates that an event, state, or relationship concluded in the specified calendar year.
-
E.
basedOnFictionalDateIn
Indicates that something is derived from, inspired by, or determined using a fictional date occurring within a specified work, timeline, or fictional context.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb609965081908f654bcb9eaaa145 |
completed | April 14, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.