Triple
T3075209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rooney family |
E64118
|
entity |
| Predicate | hasFamilyRule |
P18205
|
FINISHED |
| Object | Rooney family ownership control of Steelers voting shares |
—
|
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: Rooney family ownership control of Steelers voting shares | Statement: [Rooney family, hasFamilyRule, Rooney family ownership control of Steelers voting shares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyRule Context triple: [Rooney family, hasFamilyRule, Rooney family ownership control of Steelers voting shares]
-
A.
familyRule
chosen
Indicates a rule, norm, or guideline that governs relationships or behavior within a family context.
-
B.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
C.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
D.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
E.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada150d8e08190bde5f68e800e8feb |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.