Triple
T34573067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EDELWEISS |
E887674
|
entity |
| Predicate | associatedWithIcaoCode |
P36333
|
FINISHED |
| Object | EDW |
E887673
|
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: EDW | Statement: [EDELWEISS, associatedWithIcaoCode, EDW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithIcaoCode Context triple: [EDELWEISS, associatedWithIcaoCode, EDW]
-
A.
associatedWithICAOcode
chosen
Indicates a relationship where an entity is linked to, or identified by, a specific ICAO (International Civil Aviation Organization) code.
-
B.
associatedWithCarrierAircraft
Indicates a relationship where something is linked or connected to a carrier-based aircraft, such as being used by, transported on, or otherwise functionally related to it.
-
C.
associatedWithAirportCode
Indicates that one entity has a relationship or connection to an airport identified by a specific airport code.
-
D.
associatedWithAircraftManufacturer
Indicates that an entity has a relationship or connection with a specific aircraft manufacturer, such as collaboration, production, ownership, or other formal association.
-
E.
associatedAirlineICAOCode
Indicates the ICAO airline code that is linked to or used by the given entity (such as a flight, route, or service).
- F. None of above.
Provenance (4 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3741034cfc8190941a530c4e5eba02 |
completed | June 21, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:03 a.m.