Triple
T25812270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WIJJ |
E650143
|
entity |
| Predicate | associatedIATA |
P45234
|
FINISHED |
| Object | JOG |
—
|
NE NERFINISHED |
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: JOG | Statement: [WIJJ, associatedIATA, JOG]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedIATA Context triple: [WIJJ, associatedIATA, JOG]
-
A.
associatedWithIATAAirlineCode
Indicates that an entity is linked to or identified by a specific IATA airline code.
-
B.
associatedAirlineType
Indicates a relationship where an airline is linked to a specific classification or type (e.g., carrier category or operational class).
-
C.
associatedAirport
Indicates a relationship where an entity is linked or connected to a specific airport, typically as its relevant or corresponding airport.
-
D.
associatedWithIATATypeCode
Indicates that one entity is linked to or characterized by a specific IATA type code that classifies its role or function in air transport.
-
E.
associatedWithAirportCode
chosen
Indicates that one entity has a relationship or connection to an airport identified by a specific airport code.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: April 22, 2026, 7:11 a.m.