Triple
T22842183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LNGS |
E566110
|
entity |
| Predicate | undergroundHalls |
P110792
|
FINISHED |
| Object | three main experimental halls |
—
|
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: three main experimental halls | Statement: [LNGS, undergroundHalls, three main experimental halls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undergroundHalls Context triple: [LNGS, undergroundHalls, three main experimental halls]
-
A.
undergroundZone
chosen
Indicates that something is located in, associated with, or occurring within an area beneath the ground surface.
-
B.
undergroundBranch
Indicates that one entity is a branch or extension of another that operates or exists in a hidden, secret, or non-public manner.
-
C.
undergroundCavernLength
Indicates the measured linear extent or distance from one end to the other of an underground cavern.
-
D.
subterranean
Indicates that one entity is located beneath the surface of the ground or under another structure or area.
-
E.
undergroundTourAvailable
Indicates that guided tours taking place below ground level (such as in tunnels, caves, or basements) are offered at this location or for this attraction.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e855abc8190b9cf8cc515090a7f |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:35 p.m.