Triple
T28878518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwood family |
E732345
|
entity |
| Predicate | knownForPerson |
P42032
|
FINISHED |
| Object | Brandy Norwood |
—
|
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: Brandy Norwood | Statement: [Norwood family, knownForPerson, Brandy Norwood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForPerson Context triple: [Norwood family, knownForPerson, Brandy Norwood]
-
A.
nowKnownFor
Indicates that an entity is currently recognized or notable for a particular role, attribute, achievement, or association.
-
B.
knownForAct
Indicates that an entity is recognized or notable for performing a particular act or action.
-
C.
namedForKnownFor
Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
-
D.
alsoKnownFor
Indicates that an entity is additionally recognized or noted for another work, role, achievement, or characteristic beyond its primary association.
-
E.
refersToPersonKnownFor
chosen
Indicates that one entity makes reference to a person who is notable or recognized for some specific role, achievement, or characteristic.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 28, 2026, 7:40 a.m.