Triple
T27685588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donte |
E698019
|
entity |
| Predicate | notablyBornBy |
P201617
|
FINISHED |
| Object | Donte DiVincenzo |
—
|
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: Donte DiVincenzo | Statement: [Donte, notablyBornBy, Donte DiVincenzo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablyBornBy Context triple: [Donte, notablyBornBy, Donte DiVincenzo]
-
A.
notableBirth
Indicates that one entity is the place or context in which another entity was born, highlighting a notable birth event.
-
B.
notableMemberBirthName
Indicates the birth name of a notable member associated with an entity.
-
C.
hasNotableFieldOfBornPerson
Indicates that a person is notably associated with or recognized for a particular field related to their birth (such as birthplace’s notable domain or the field for which they are known).
-
D.
notablyBorneBy
Indicates that something is especially or prominently carried, supported, or borne by a particular entity, in a way that is distinctive or noteworthy.
-
E.
wasBornInto
Indicates that an entity entered existence as a member of a particular family, social group, or circumstance at birth.
- F. None of above. chosen
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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a000efe971081909de03f875a7ad6cc |
completed | May 10, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a000c4ffe788190a5757af60aadd9f3 |
completed | May 10, 2026, 4:40 a.m. |
| PDg | Predicate description generation | batch_6a000efdbe948190b4bfa9871aa1a7ee |
completed | May 10, 2026, 4:52 a.m. |
Created at: April 27, 2026, 2:49 p.m.