Triple
T6064200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EHN3 |
E135113
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | EHN3 |
E135113
|
NE 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: EHN3 | Statement: [EHN3, hasAbbreviation, EHN3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EHN3 Context triple: [EHN3, hasAbbreviation, EHN3]
-
A.
EHN3
chosen
EHN3 is a large experimental hall in CERN’s North Area used primarily for fixed-target and test-beam particle physics experiments.
-
B.
EHN1
EHN1 is a large experimental hall in CERN’s North Area used for fixed-target and test-beam particle physics experiments served by the Super Proton Synchrotron.
-
C.
EHN4
EHN4 is a large experimental hall in CERN’s North Area used for fixed-target and test-beam particle physics experiments served by the Super Proton Synchrotron.
-
D.
EH53
EH53 is a postcode district in the EH (Edinburgh) area of Scotland, covering Mid Calder and its surrounding locality in West Lothian.
-
E.
EHTE
EHTE is the ICAO airport code for Teuge Airport, a general aviation airfield in the Netherlands.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05723c91c819090b4d4672e72f9f3 |
completed | March 22, 2026, 8:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c11d1e61188190aea0e2b1945ca682 |
completed | March 23, 2026, 10:59 a.m. |
Created at: March 22, 2026, 4:10 p.m.