Triple
T1354655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SFO Museum |
E28959
|
entity |
| Predicate | servesLocation |
P6789
|
FINISHED |
| Object | San Francisco International Airport terminals |
—
|
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: San Francisco International Airport terminals | Statement: [SFO Museum, servesLocation, San Francisco International Airport terminals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesLocation Context triple: [SFO Museum, servesLocation, San Francisco International Airport terminals]
-
A.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
-
B.
serviceLocation
Indicates the place or address where a service is provided, performed, or made available to the relevant party.
-
C.
servesUnder
Indicates that one entity works in a subordinate role under the authority, command, or supervision of another entity.
-
D.
servesVenue
chosen
Indicates that an entity provides services or functions in support of a particular venue.
-
E.
servesFacility
Indicates that one entity provides services or support to a particular facility as its client, target, or area of operation.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c28afc848190925d8b2f9aeac12d |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.