Triple
T37568340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | edoi1259 |
E934621
|
entity |
| Predicate | appliesToBranchOf |
P68156
|
FINISHED |
| Object | Niger-Congo |
—
|
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: Niger-Congo | Statement: [edoi1259, appliesToBranchOf, Niger-Congo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToBranchOf Context triple: [edoi1259, appliesToBranchOf, Niger-Congo]
-
A.
relatesToBranch
chosen
Indicates a general association or connection between an entity and a specific branch (such as a subdivision, offshoot, or subunit) within a larger structure or system.
-
B.
usedByBranch
Indicates that something (such as a resource, configuration, or component) is utilized or depended upon by a particular branch.
-
C.
isUniqueBranchOf
Indicates that one branch is the sole or distinct sub-branch associated with a particular parent entity or structure.
-
D.
isPartOfBranchTypically
Indicates that something is typically a component or subdivision within a larger branch.
-
E.
representedBranch
Indicates that one entity serves as a representative or proxy for a particular branch of another entity or organization.
- 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffb1f0b03c81909ddb81f07ce74e88 |
completed | May 9, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ffb1662b2481908582e0612744f4c5 |
completed | May 9, 2026, 10:12 p.m. |
Created at: May 3, 2026, 4:17 p.m.