Triple
T4573500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitch Christie |
E123089
|
entity |
| Predicate | testRecord |
P57797
|
FINISHED |
| Object | unbeaten as Springbok coach |
—
|
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: unbeaten as Springbok coach | Statement: [Kitch Christie, testRecord, unbeaten as Springbok coach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testRecord Context triple: [Kitch Christie, testRecord, unbeaten as Springbok coach]
-
A.
testDetail
Indicates that there is specific, often granular information or attributes associated with a particular test or testing instance.
-
B.
launchRecord
Indicates the act of initiating or starting a recorded instance of a process, event, or operation.
-
C.
recordingOf
Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
-
D.
trackRecordUsedFor
Indicates that a track record is utilized as a basis or input for some subsequent decision, evaluation, or process.
-
E.
tests
Indicates that one entity examines, evaluates, or checks another entity or condition to determine its properties, performance, or correctness.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c89a5c81909a78bf0ac64777ad |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:10 p.m.