Triple
T35524826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don't Be Tardy |
E1026643
|
entity |
| Predicate | featuresFamilyMember |
P40767
|
FINISHED |
| Object | Kroy Biermann |
E2145588
|
NE 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: Kroy Biermann | Statement: [Don't Be Tardy, featuresFamilyMember, Kroy Biermann]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresFamilyMember Context triple: [Don't Be Tardy, featuresFamilyMember, Kroy Biermann]
-
A.
featuresFamilyFrom
Indicates that something includes or presents a family originating from or associated with a specified source.
-
B.
platformFamilyMember
Indicates that one platform is considered a member or variant within the family or group defined by another platform.
-
C.
featuresFamily
chosen
Indicates that something includes, presents, or highlights a family as a central element or subject.
-
D.
uniqueFamilyMember
Indicates that one entity is a family member of another in a way that is distinct and not shared by any other family member.
-
E.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
- F. None of above.
Provenance (4 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a385bc67de88190bd838cb0525bd6d0 |
completed | June 21, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.