Triple
T17337366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LXR |
E420973
|
entity |
| Predicate | associatedWithICAOCode |
P419
|
FINISHED |
| Object | HELX |
E420974
|
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: HELX | Statement: [LXR, associatedWithICAOCode, HELX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HELX Context triple: [LXR, associatedWithICAOCode, HELX]
-
A.
HELX
chosen
HELX is the ICAO airport code for Luxor International Airport, a major gateway to the historic city of Luxor in Egypt.
-
B.
Helix
Helix is a science fiction horror television series centered on a team of CDC scientists investigating a deadly outbreak at a remote Arctic research facility.
-
C.
Helix
Helix is an interactive light-based art installation by Jen Lewin that invites public participation through responsive, immersive illumination.
-
D.
Helix
Helix is a multi-launch steel roller coaster at the Liseberg amusement park in Gothenburg, Sweden, known for its intense inversions and terrain-hugging layout.
-
E.
Helix
Helix is the NATO reporting name for a series of Soviet and Russian Kamov naval helicopters known for their distinctive coaxial rotor design and use in maritime roles.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a12e1288190a81c30d6e1e9652f |
completed | April 19, 2026, 2:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a018c5474788190936840effee2a8f5 |
completed | May 11, 2026, 7:59 a.m. |
Created at: April 10, 2026, 5:43 a.m.