Triple
T3756980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chronicle |
E82070
|
entity |
| Predicate | eraSystemUsed |
P29664
|
FINISHED |
| Object | Olympiads |
—
|
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: Olympiads | Statement: [Chronicle, eraSystemUsed, Olympiads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraSystemUsed Context triple: [Chronicle, eraSystemUsed, Olympiads]
-
A.
eraSystem
chosen
Indicates a temporal classification relationship where an entity is associated with a particular era or chronological system used to organize time.
-
B.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
C.
usedBySystem
Indicates that something is utilized or operated by a particular system.
-
D.
associatedSystem
Indicates that one entity is functionally or contextually linked to a particular system with which it interacts or to which it belongs.
-
E.
eraDeveloped
Indicates that something was created, formed, or came into existence during a specific historical era or time period.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbbe7a6081909b0f835a77941300 |
completed | March 8, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69adc04c851c8190ae5eaebf36df539b |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.