Triple
T28467341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brittany Favre |
E720329
|
entity |
| Predicate | sportingFamilyConnection |
P78303
|
FINISHED |
| Object | American football |
—
|
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: American football | Statement: [Brittany Favre, sportingFamilyConnection, American football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportingFamilyConnection Context triple: [Brittany Favre, sportingFamilyConnection, American football]
-
A.
sportsAssociationViaFamily
Indicates a relationship where an entity is associated with a sport or sports organization through a family member’s involvement rather than their own direct participation.
-
B.
memberOfSportsFamily
chosen
Indicates that an entity belongs to a family or lineage known for involvement in sports or athletic activities.
-
C.
familyConnectionTo
Indicates a familial relationship or bond that exists between two entities, such as by blood, marriage, or adoption.
-
D.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
-
E.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 2:45 a.m.