Triple
T29893927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Declaration of a New Order |
E759224
|
entity |
| Predicate | inUniverseDateApproximation |
P877
|
FINISHED |
| Object | 19 BBY |
—
|
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: 19 BBY | Statement: [Declaration of a New Order, inUniverseDateApproximation, 19 BBY]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseDateApproximation Context triple: [Declaration of a New Order, inUniverseDateApproximation, 19 BBY]
-
A.
inUniverseDate
Indicates that an entity is associated with or occurs on a specific date within a fictional or defined universe’s internal timeline.
-
B.
approximateDateChange
Indicates that the date associated with an entity has changed in an inexact or estimated manner rather than to a precisely known new date.
-
C.
unificationApproximateDate
Indicates that two entities became unified or merged around an estimated or approximate date rather than a precisely known time.
-
D.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
E.
inUniverseAge
Indicates the age of an entity as measured within the timeline or continuity of a specific fictional or defined universe.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 29, 2026, 6:03 p.m.