Triple
T30960027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bole language |
E788784
|
entity |
| Predicate | hasSubjectPeople |
P197298
|
FINISHED |
| Object | Bole people |
—
|
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: Bole people | Statement: [Bole language, hasSubjectPeople, Bole people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubjectPeople Context triple: [Bole language, hasSubjectPeople, Bole people]
-
A.
hasHumanSubject
Indicates that an entity serves as the human participant or subject involved in an action, event, or relation.
-
B.
hasSubjectRoleIn
Indicates that an entity serves in a specific subject role within a particular context, situation, or relationship.
-
C.
hasSubjectOfDisplay
Indicates that one entity serves as the subject or main focus of another entity’s display or presentation.
-
D.
hasTypicalSubject
Indicates that something is commonly or characteristically used as the subject (agent or topic) of a given relation or action.
-
E.
hasNotableSubject
Indicates that an entity is associated with a subject that is particularly significant, prominent, or noteworthy in relation to it.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
| PDg | Predicate description generation | batch_69fe86c98d688190a99d5dcb14e2dc95 |
completed | May 9, 2026, 12:58 a.m. |
Created at: April 29, 2026, 8:54 p.m.