Triple
T35310987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eweka I |
E1019769
|
entity |
| Predicate | traditionalChronology |
P31438
|
FINISHED |
| Object | 13th century |
—
|
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: 13th century | Statement: [Eweka I, traditionalChronology, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalChronology Context triple: [Eweka I, traditionalChronology, 13th century]
-
A.
eraChronology
Indicates the temporal ordering relationship that places an era within a specific position in a broader historical or chronological sequence.
-
B.
chronologyType
Indicates the type or system of chronological ordering or dating applied to an event, period, or sequence.
-
C.
reignChronology
Indicates the temporal order or sequence in which different reigns or periods of rule occur relative to one another.
-
D.
traditionallyDated
chosen
Indicates that something is assigned a date based on traditional or customary chronology rather than on firmly established historical or scientific evidence.
-
E.
relativeChronology
Indicates a temporal ordering relationship that specifies how one event or state is positioned in time relative to another (e.g., earlier, later, or overlapping).
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
Created at: May 3, 2026, 4:03 p.m.