Triple
T36337441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clone Wars era |
E894823
|
entity |
| Predicate | chronologicallyStartsWith |
P197036
|
FINISHED |
| Object | Battle of Geonosis |
—
|
NE NERFINISHED |
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: Battle of Geonosis | Statement: [Clone Wars era, chronologicallyStartsWith, Battle of Geonosis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicallyStartsWith Context triple: [Clone Wars era, chronologicallyStartsWith, Battle of Geonosis]
-
A.
chronologicallyAfter
Indicates that one event or state occurs later in time than another.
-
B.
chronologicallyBetween
Indicates that one event or time point occurs after a first reference point and before a second reference point in temporal order.
-
C.
chronologicallyBelongsTo
Indicates that one temporal entity or event falls within, or is properly associated with, a specific time period or chronological grouping.
-
D.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
E.
chronologicalCriterion
Indicates a temporal condition that orders or selects entities based on when they occur or exist relative to one another.
- 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
| PDg | Predicate description generation | batch_69fe744e9ee081909b362fc8609bc744 |
completed | May 8, 2026, 11:39 p.m. |
Created at: May 3, 2026, 4:09 p.m.