Triple
T29449741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sigui ceremony |
E746941
|
entity |
| Predicate | notableCycle |
P204287
|
FINISHED |
| Object | 1967–1973 Sigui cycle |
—
|
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: 1967–1973 Sigui cycle | Statement: [Sigui ceremony, notableCycle, 1967–1973 Sigui cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCycle Context triple: [Sigui ceremony, notableCycle, 1967–1973 Sigui cycle]
-
A.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
B.
notableArc
Indicates a significant or defining narrative development, transformation, or storyline involving the related entities.
-
C.
notableCrossing
Indicates that one entity is a significant or well-known crossing point (such as a bridge, pass, or intersection) associated with another entity.
-
D.
notableCircuit
Indicates that an entity is recognized as a significant or noteworthy circuit, such as an important electrical, racing, or logical circuit.
-
E.
notableRepeatBy
Indicates that an action, event, or pattern occurs repeatedly and is notably performed, exhibited, or instantiated by a particular entity.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a036b0755888190a68a673664f0ea46 |
completed | May 12, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_6a036228676c8190aac9c90f7d8cedf7 |
completed | May 12, 2026, 5:23 p.m. |
| PDg | Predicate description generation | batch_6a036b0678448190be865dd52792efab |
completed | May 12, 2026, 6:01 p.m. |
Created at: April 28, 2026, 3:31 p.m.