Triple
T32184257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nednhi Ndé |
E822062
|
entity |
| Predicate | selfDesignationIncludes |
P28298
|
FINISHED |
| Object | Ndé |
—
|
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: Ndé | Statement: [Nednhi Ndé, selfDesignationIncludes, Ndé]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selfDesignationIncludes Context triple: [Nednhi Ndé, selfDesignationIncludes, Ndé]
-
A.
previousDesignationIncludes
Indicates that an entity’s earlier or former official name, title, or designation contained the specified value.
-
B.
isDesignatedAccordingTo
Indicates that an entity has a particular status, role, or classification as formally specified by a given authority, standard, or designation scheme.
-
C.
hasInternalDesignationFor
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
-
D.
usedAsSelfDesignation
chosen
Indicates that an entity is used by a person or group as a term to refer to or identify themselves.
-
E.
hasDesignationBy
Indicates that one entity has been formally assigned or labeled with a specific designation by 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bab75a948190a531ac204aee4fca |
completed | May 3, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:35 a.m.