Triple
T95170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Large Hadron Collider |
E1914
|
entity |
| Predicate | firstLongShutdown |
P3953
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Large Hadron Collider, firstLongShutdown, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLongShutdown Context triple: [Large Hadron Collider, firstLongShutdown, 2013]
-
A.
inForceUntil
Indicates that a condition, rule, or agreement remains valid and operative up to a specified time or event.
-
B.
maintenance
Indicates that an entity performs, requires, or is involved in upkeep, repair, or preservation activities for another entity or system.
-
C.
firstDeployed
Indicates the time or event when something (such as a system, product, or resource) was initially put into active use or operation.
-
D.
firstOccupied
Indicates that an entity was the initial or earliest occupant of a particular place, position, or resource.
-
E.
firstStandardApproved
Indicates that an entity is the earliest or initial standard that has received formal approval.
- 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_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. |
| PDg | Predicate description generation | batch_69a24fed6b8c819080a6c0cd3b16e6bd |
completed | Feb. 28, 2026, 2:16 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.