Triple
T192580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MoEDAL |
E3751
|
entity |
| Predicate | operationalEnvironment |
P853
|
FINISHED |
| Object | underground experimental cavern at CERN |
—
|
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: underground experimental cavern at CERN | Statement: [MoEDAL, operationalEnvironment, underground experimental cavern at CERN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalEnvironment Context triple: [MoEDAL, operationalEnvironment, underground experimental cavern at CERN]
-
A.
environmentType
chosen
Indicates the kind or category of environment associated with an entity or situation.
-
B.
operatingSystem
Indicates that one entity is the operating system running on, or used by, another entity.
-
C.
operationalLayer
Indicates that one entity functions as an operational layer or level through which another entity’s activities, processes, or services are executed or managed.
-
D.
operatesSystem
Indicates that an entity actively controls, manages, or runs a particular system.
-
E.
operationalCeiling
Indicates the maximum altitude at which an entity (such as an aircraft or system) is designed or permitted to operate effectively and safely.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a259669ba08190a5be1d2e10e70b27 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a2567567508190b3a41329a15c7156 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.