Triple
T95169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Large Hadron Collider |
E1914
|
entity |
| Predicate | firstPhysicsRunStart |
P3273
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Large Hadron Collider, firstPhysicsRunStart, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPhysicsRunStart Context triple: [Large Hadron Collider, firstPhysicsRunStart, 2009]
-
A.
operationStart
Indicates the point in time or event at which a specific operation or process begins.
-
B.
firstOccupied
Indicates that an entity was the initial or earliest occupant of a particular place, position, or resource.
-
C.
startPoint
Indicates the initial location or position from which an object, path, or action begins.
-
D.
firstDemonstrated
Indicates that one entity was the earliest to show, prove, or exemplify a particular concept, method, or capability in relation to another entity or context.
-
E.
firstDeployed
chosen
Indicates the time or event when something (such as a system, product, or resource) was initially put into active use or operation.
- 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.