Triple
T95171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Large Hadron Collider |
E1914
|
entity |
| Predicate | firstLongShutdownEnd |
P2818
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Large Hadron Collider, firstLongShutdownEnd, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLongShutdownEnd Context triple: [Large Hadron Collider, firstLongShutdownEnd, 2015]
-
A.
concludedAt
chosen
Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
-
B.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
C.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
-
D.
inForceUntil
Indicates that a condition, rule, or agreement remains valid and operative up to a specified time or event.
-
E.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24ebb3da08190a8b82564f33cde3b |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.