Triple
T17335482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Wars canon |
E420923
|
entity |
| Predicate | followsChronologySystem |
P88531
|
FINISHED |
| Object | Before the Battle of Yavin |
—
|
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: Before the Battle of Yavin | Statement: [Star Wars canon, followsChronologySystem, Before the Battle of Yavin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsChronologySystem Context triple: [Star Wars canon, followsChronologySystem, Before the Battle of Yavin]
-
A.
followsInReleaseChronology
Indicates that one entity is released after another in a chronological sequence of releases.
-
B.
involvesChronology
Indicates that the relationship or action explicitly depends on, references, or organizes events according to their order or position in time.
-
C.
chronologyType
chosen
Indicates the type or system of chronological ordering or dating applied to an event, period, or sequence.
-
D.
chronologyUsedBy
Indicates that a particular system, method, or scheme of chronological ordering is employed or adopted by a given entity.
-
E.
followsGregorianCalendar
Indicates that the entity uses or adheres to the Gregorian calendar system for dating and timekeeping.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a1125d88190b67243b30d93ce1c |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:43 a.m.