Triple
T25274366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABC Motsepe League |
E633654
|
entity |
| Predicate | hasDivisionStatus |
P118218
|
FINISHED |
| Object | third division |
—
|
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: third division | Statement: [ABC Motsepe League, hasDivisionStatus, third division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDivisionStatus Context triple: [ABC Motsepe League, hasDivisionStatus, third division]
-
A.
hasDivisionCode
Indicates that an entity is associated with a specific division identifier or code within an organizational or classification structure.
-
B.
containsDivision
Indicates that one entity includes or encompasses a subdivision or internal division of another entity.
-
C.
divisionStatus
chosen
Indicates the current operational or organizational state of a division within a larger entity.
-
D.
hasDivisionLevel
Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
-
E.
hasDivisionRole
Indicates that an entity holds a specific role or position within a particular division of an 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 21, 2026, 1:17 p.m.