Triple
T15334633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Sydney International Airport |
E366629
|
entity |
| Predicate | curfew |
P118155
|
FINISHED |
| Object | no curfew planned |
—
|
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: no curfew planned | Statement: [Western Sydney International Airport, curfew, no curfew planned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curfew Context triple: [Western Sydney International Airport, curfew, no curfew planned]
-
A.
nightUse
Indicates that an entity is used, active, or intended specifically during the night.
-
B.
nightService
Indicates that a service operates or is available during nighttime hours.
-
C.
associatedNightTiming
Indicates a relationship where an event, action, or condition is linked specifically to a time period occurring during the night.
-
D.
isNocturnal
Indicates that an entity is primarily active during the night and rests during the day.
-
E.
sleepCurse
Indicates a condition where one entity has magically imposed or is affected by a curse that causes unnatural or enforced sleep.
- 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_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. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:17 a.m.