Triple
T28690861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brittany Brees |
E729279
|
entity |
| Predicate | hasPartnerRoleWith |
P1136
|
FINISHED |
| Object | Drew Brees |
—
|
NE NERFINISHED |
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: Drew Brees | Statement: [Brittany Brees, hasPartnerRoleWith, Drew Brees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartnerRoleWith Context triple: [Brittany Brees, hasPartnerRoleWith, Drew Brees]
-
A.
hasPartnershipRole
Indicates that an entity holds a specific role or function within a partnership relationship with another entity.
-
B.
hasConventionalPartnerRole
Indicates that one entity holds a standard or customary partner role in relation to another entity within a defined partnership context.
-
C.
hasPartner
chosen
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
D.
hasCompanionRoleIn
Indicates that an entity serves in a companion or supporting role within a specified context, activity, or relationship.
-
E.
hasCompanionRoleTo
Indicates that one entity serves in a companion or supporting role in relation to another entity.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 28, 2026, 5:36 a.m.