Triple
T9135426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles International Airport Theme Building |
E219187
|
entity |
| Predicate | restaurantClosed |
P77023
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Los Angeles International Airport Theme Building, restaurantClosed, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restaurantClosed Context triple: [Los Angeles International Airport Theme Building, restaurantClosed, 2014]
-
A.
EncounterRestaurantClosure
Indicates that an entity experiences or comes across the situation of a restaurant being closed.
-
B.
restaurantClosureDate
chosen
Indicates the date on which a restaurant ceases or ceased operations, marking its official closure.
-
C.
closedVenue
Indicates that a venue is not open or available for use during a given time or event.
-
D.
closedAsHotel
Indicates that an establishment ceased operating in general and specifically stopped functioning as a hotel.
-
E.
EncounterRestaurantOpening
Indicates a situation where an entity comes across or experiences the opening or start of operations of a restaurant.
- 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8df68108190bb2df0583c5ad481 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.