Triple
T1228509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TJSJ |
E26380
|
entity |
| Predicate | hasGeneralAviationFacilities |
P24735
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [TJSJ, hasGeneralAviationFacilities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeneralAviationFacilities Context triple: [TJSJ, hasGeneralAviationFacilities, yes]
-
A.
hasNearbyGeneralAviationAirport
Indicates that an entity is located close to a general aviation airport, such that the airport can reasonably serve it for non-commercial or private air traffic.
-
B.
aircraftFacility
Indicates that a facility is designed, equipped, or used to support the operation, maintenance, or accommodation of aircraft.
-
C.
containsAirfield
Indicates that a location or area includes at least one airfield within its boundaries.
-
D.
isCivilAirport
Indicates that an airport is designated and used primarily for civilian (non-military) aviation operations.
-
E.
hasHeliport
Indicates that an entity possesses or is equipped with a heliport facility for helicopter landing and takeoff.
- F. None of above. chosen
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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be3c5d4c819087f9e9e37204c3be |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb65d61c8190bf0424ea0019a98b |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bbf83584819088c69366f58586cc |
completed | March 1, 2026, 10:21 p.m. |
Created at: March 1, 2026, 7:47 p.m.