Triple
T17335591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lothal |
E420926
|
entity |
| Predicate | governmentEra |
P34083
|
FINISHED |
| Object | Galactic Empire era |
—
|
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: Galactic Empire era | Statement: [Lothal, governmentEra, Galactic Empire era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentEra Context triple: [Lothal, governmentEra, Galactic Empire era]
-
A.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
-
B.
dynasticEraName
Indicates the named historical period or era associated with a particular dynasty’s rule.
-
C.
governmentFormDuringEra
Indicates the specific form or system of government that was in place during a particular historical era or time period.
-
D.
dateEnactedEraName
Indicates that a law, policy, or formal act was enacted during a specific named historical era.
-
E.
partOfEra
chosen
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
- 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.