Triple
T7706326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuengling Brewery |
E174624
|
entity |
| Predicate | hasHistoricSiteStatus |
P1098
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Yuengling Brewery, hasHistoricSiteStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricSiteStatus Context triple: [Yuengling Brewery, hasHistoricSiteStatus, true]
-
A.
hasHistoricSite
chosen
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
-
B.
isHistoricPlace
Indicates that a place holds recognized historical significance, often due to its age, events, or cultural importance.
-
C.
heritageStatus
Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
-
D.
historicAreaIncludes
Indicates that a designated historic area geographically contains or encompasses another place or feature within its boundaries.
-
E.
historicalStatusOf
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
- 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_69c6995b3e8c8190833108f883d5f53c |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.