Triple
T4828427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanford Linear Collider |
E107881
|
entity |
| Predicate | colliderGeometry |
P59895
|
FINISHED |
| Object | linear |
—
|
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: linear | Statement: [Stanford Linear Collider, colliderGeometry, linear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colliderGeometry Context triple: [Stanford Linear Collider, colliderGeometry, linear]
-
A.
collider
Indicates that two or more entities participate together in operating or utilizing a particle collider or similar high-energy physics experimental facility.
-
B.
colliderType
Indicates the type or category of physical collision behavior defined for an object in a simulation or physics system.
-
C.
colliderUsed
Indicates that a particular collider or collision-detection component is employed or involved in an interaction or event between entities.
-
D.
collisionDomain
Indicates that two or more network entities share the same collision domain, meaning their transmissions can interfere and cause packet collisions with each other.
-
E.
collisionSystem
Indicates a physical interaction where two or more entities impact or collide with each other within a defined system or environment.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1fe130819087ae01309f96a0c8 |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6dda5e808190a26ec85e4499d8e4 |
completed | March 20, 2026, 3:55 p.m. |
Created at: March 20, 2026, 1:24 p.m.