Triple
T36274581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worldwide LHC Computing Grid |
E892770
|
entity |
| Predicate | Tier‑0LocatedAt |
P19797
|
FINISHED |
| Object | CERN |
—
|
NE NERFINISHED |
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: CERN | Statement: [Worldwide LHC Computing Grid, Tier‑0LocatedAt, CERN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Tier‑0LocatedAt Context triple: [Worldwide LHC Computing Grid, Tier‑0LocatedAt, CERN]
-
A.
areLocatedAt
Indicates that one or more entities occupy or exist at a specific location or place.
-
B.
dataCenterLocation
chosen
Indicates the geographical or physical location where a data center is situated or hosted.
-
C.
locatedOver
Indicates that one entity is positioned above another entity, typically without direct contact, in a vertical or overhead spatial relationship.
-
D.
terminusLocatedOn
Indicates that the endpoint or final stop of one entity (such as a route or line) is situated on or at another entity (such as a street, line, or location).
-
E.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.