Triple
T15334632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Sydney International Airport |
E366629
|
entity |
| Predicate | plannedOperations |
P62980
|
FINISHED |
| Object | 24-hour operations |
—
|
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: 24-hour operations | Statement: [Western Sydney International Airport, plannedOperations, 24-hour operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedOperations Context triple: [Western Sydney International Airport, plannedOperations, 24-hour operations]
-
A.
operatorPlanned
Indicates that an operator has scheduled or arranged a specific action, process, or operation to occur.
-
B.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
C.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
D.
plannedService
chosen
Indicates that a service is scheduled or intended to be provided, but has not yet occurred.
-
E.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e03c5f081908e4d14dbdbc7f7a6 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.