Triple
T21554767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putnam County Playhouse |
E531860
|
entity |
| Predicate | hasVenueProperty |
P144221
|
FINISHED |
| Object | historic building |
—
|
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: historic building | Statement: [Putnam County Playhouse, hasVenueProperty, historic building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVenueProperty Context triple: [Putnam County Playhouse, hasVenueProperty, historic building]
-
A.
hasVenueIn
Indicates that an event, activity, or occurrence takes place at a specific venue located within a particular geographic area or location.
-
B.
hasVenueFor
Indicates that one entity provides or serves as the location or setting where an event, activity, or function takes place for another entity.
-
C.
hasPrincipalVenue
Indicates that an entity has a primary or main venue where its activities, events, or operations predominantly take place.
-
D.
homeVenueOwned
Indicates that the specified home venue is legally owned or possessed by the associated entity.
-
E.
hasVenueFunction
Indicates that a venue serves a particular function or role (such as hosting events, performances, or specific activities).
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2de1c248190b303a4a55b022374 |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:29 p.m.