Triple
T4021435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevada gubernatorial inaugurations |
E91286
|
entity |
| Predicate | mayOccurOn |
P12708
|
FINISHED |
| Object | January |
—
|
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: January | Statement: [Nevada gubernatorial inaugurations, mayOccurOn, January]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayOccurOn Context triple: [Nevada gubernatorial inaugurations, mayOccurOn, January]
-
A.
mayResultIn
Indicates that one entity has the potential to cause, lead to, or bring about another entity or outcome, without guaranteeing that it will occur.
-
B.
endsOn
Indicates that one entity terminates or concludes precisely at the boundary or endpoint of another entity.
-
C.
mayPresent
Indicates that one entity is permitted or authorized to present, display, or introduce another entity or item.
-
D.
occursWhen
chosen
Indicates that one event or condition happens at the same time or is triggered under the circumstances defined by another event or condition.
-
E.
mayExtendTo
Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefacb4c208190b8dd595a534850b2 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.