Triple
T36655258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 4 (Ninoy Aquino International Airport) |
E904969
|
entity |
| Predicate | hasSimpleFacilities |
P196524
|
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: [Terminal 4 (Ninoy Aquino International Airport), hasSimpleFacilities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSimpleFacilities Context triple: [Terminal 4 (Ninoy Aquino International Airport), hasSimpleFacilities, yes]
-
A.
hasFacilities
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
B.
hasLimitedFacilities
Indicates that an entity provides only a restricted or insufficient range or quality of facilities or services.
-
C.
hasGoodsFacilities
Indicates that a location or entity is equipped with facilities for handling, storing, or processing goods or cargo.
-
D.
hasMaintenanceFacilities
Indicates that one entity provides or contains facilities where the other entity can be serviced, repaired, or maintained.
-
E.
hasNotableFacility
Indicates that an entity possesses or hosts a facility that is of particular significance, prominence, or interest.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
| PDg | Predicate description generation | batch_69fe59d03a648190bbe846cb5730a477 |
completed | May 8, 2026, 9:46 p.m. |
Created at: May 3, 2026, 4:11 p.m.