Triple
T35652584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WAML |
E1030191
|
entity |
| Predicate | associatedCityAirport |
P51581
|
FINISHED |
| Object | Palu |
E80399
|
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: Palu | Statement: [WAML, associatedCityAirport, Palu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCityAirport Context triple: [WAML, associatedCityAirport, Palu]
-
A.
associatedAirport
Indicates a relationship where an entity is linked or connected to a specific airport, typically as its relevant or corresponding airport.
-
B.
associatedAirportFocusCityFor
Indicates that an airport serves as a designated focus city for a particular airline or carrier.
-
C.
otherAirportOfCity
Indicates that the subject airport is another airport serving the same city as the object airport.
-
D.
associatedAirportServes
chosen
Indicates that a given airport provides service to, or is used by, the associated entity (such as a city, region, or facility).
-
E.
associatedHubAirport
Indicates that one entity serves as a primary or hub airport functionally linked to the other entity.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38914f56c88190828a8f3bbd78a053 |
completed | June 22, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.