Triple
T9122580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | isihlangu |
E218889
|
entity |
| Predicate | reinforcement |
P3261
|
FINISHED |
| Object | wooden or cane spine |
—
|
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: wooden or cane spine | Statement: [isihlangu, reinforcement, wooden or cane spine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reinforcement Context triple: [isihlangu, reinforcement, wooden or cane spine]
-
A.
reinforcedIn
Indicates that one entity is strengthened, supported, or made more robust within, or as a result of conditions in, another entity or context.
-
B.
reinforcedPrinciple
Indicates that one entity has strengthened, supported, or validated a principle associated with another entity, making that principle more firmly established or accepted.
-
C.
strengthens
chosen
Indicates that one entity increases the power, effectiveness, or resilience of another.
-
D.
backing
Indicates providing support, endorsement, or financial/resources assistance to someone or something, often enabling or strengthening their actions or position.
-
E.
reivindica
Indicates that an entity asserts a right to, claims ownership of, or demands recognition or restitution for something.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8b46dac8190bde88205c85f596a |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.