Triple
T32905769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mill Grove (John James Audubon Center) |
E841733
|
entity |
| Predicate | hasVisitorFacilityType |
P2836
|
FINISHED |
| Object | museum galleries |
—
|
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 galleries | Statement: [Mill Grove (John James Audubon Center), hasVisitorFacilityType, museum galleries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitorFacilityType Context triple: [Mill Grove (John James Audubon Center), hasVisitorFacilityType, museum galleries]
-
A.
hasFacilityType
chosen
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
B.
hasVisitorServices
Indicates that an entity provides services or facilities specifically intended for visitors or guests.
-
C.
hasVisitorType
Indicates the type or category of visitor associated with an entity (e.g., guest, customer, tourist, patient).
-
D.
hasVisitationType
Indicates the specific category or mode of a visit or visitation associated with an entity or event.
-
E.
hasTypeOfVisitorExperience
Indicates that an entity is associated with a particular category or kind of visitor experience it provides or involves.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 1, 2026, 1:19 a.m.