Triple
T4150396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavanaugh Flight Museum |
E89888
|
entity |
| Predicate | operatesOnSite |
P41907
|
FINISHED |
| Object | museum gift shop |
—
|
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: museum gift shop | Statement: [Cavanaugh Flight Museum, operatesOnSite, museum gift shop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesOnSite Context triple: [Cavanaugh Flight Museum, operatesOnSite, museum gift shop]
-
A.
operatesOnSiteType
Indicates that an entity conducts its operations or activities at, or in association with, a specified type of site or location.
-
B.
operatedWebsite
Indicates that one entity runs, manages, or controls the functioning of a particular website.
-
C.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
D.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
E.
operateIn
chosen
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
- 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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af033ef6648190adde17f943d89c78 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018c101081909070da5b11e5eb3d |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.