Triple
T24369484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tswa-Ronga group |
E614290
|
entity |
| Predicate | standardizedMember |
P73395
|
FINISHED |
| Object | Xitsonga |
—
|
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: Xitsonga | Statement: [Tswa-Ronga group, standardizedMember, Xitsonga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizedMember Context triple: [Tswa-Ronga group, standardizedMember, Xitsonga]
-
A.
hasStandardizedMember
chosen
Indicates that an entity includes or is associated with a member that conforms to a defined standard or standardized specification.
-
B.
standardizedBy
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
-
C.
representsMember
Indicates that one entity is a member or constituent part of another entity, such as an individual belonging to a group or organization.
-
D.
standardizedFor
Indicates that something has been adjusted or converted to conform to a common standard, format, or reference so it can be consistently compared or used.
-
E.
stableMember
Indicates that an entity remains a consistent, long-term member of a particular group 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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2938a4f188190932af66f57be0756 |
completed | April 29, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:01 a.m.