Triple
T2358871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luo people |
E47222
|
entity |
| Predicate | namingCustom |
P1217
|
FINISHED |
| Object | names based on circumstances of birth |
—
|
LITERAL 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: names based on circumstances of birth | Statement: [Luo people, namingCustom, names based on circumstances of birth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingCustom Context triple: [Luo people, namingCustom, names based on circumstances of birth]
-
A.
coNamedWith
Indicates that two or more entities share the same name or are designated by an identical label.
-
B.
namingStructure
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
-
C.
usesNamingSystem
chosen
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
-
D.
givenNameFor
Indicates that one entity is the personal first name assigned to or used for another entity.
-
E.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc720b9048190a5d3b19e5e1f373a |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:55 p.m.