Triple
T7706303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuengling Brewery |
E174624
|
entity |
| Predicate | numberOfGenerationsOfFamilyOwnership |
P52584
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [Yuengling Brewery, numberOfGenerationsOfFamilyOwnership, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfGenerationsOfFamilyOwnership Context triple: [Yuengling Brewery, numberOfGenerationsOfFamilyOwnership, 6]
-
A.
multiGenerationOwnershipOf
Indicates that ownership of something extends across multiple generations within the same family or lineage.
-
B.
hasNumberOfForfeda
Indicates a relationship where an entity is associated with a specific count of forfeda (additional Ogham letters).
-
C.
hasGenerations
chosen
Indicates a relationship where an entity is associated with one or more successive generational levels or cohorts derived from it.
-
D.
franchiseFoundedByFamily
Indicates that a franchise was originally established or created by a family or family members.
-
E.
lifetimeInGenerations
Indicates the number of successive generations over which something (e.g., an effect, trait, or validity) persists or remains applicable.
- 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.