Triple
T95206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Large Hadron Collider |
E1914
|
entity |
| Predicate | coolingMedium |
P1272
|
FINISHED |
| Object | liquid helium |
—
|
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: liquid helium | Statement: [Large Hadron Collider, coolingMedium, liquid helium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coolingMedium Context triple: [Large Hadron Collider, coolingMedium, liquid helium]
-
A.
waterType
Indicates the specific kind or category of water associated with an entity (e.g., fresh, salt, brackish).
-
B.
environmentalCondition
Indicates the state or characteristics of the surrounding physical environment that affect or describe a situation, process, or entity.
-
C.
hasAtmosphere
Indicates that an astronomical body possesses a surrounding layer of gases held by its gravity.
-
D.
involvesParticleTransfer
Indicates that the relationship or action includes the movement or exchange of discrete particles from one entity to another.
-
E.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
- 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.