Triple
T16426246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Incwala ceremony |
E398949
|
entity |
| Predicate | publicPhase |
P5784
|
FINISHED |
| Object | outer Incwala |
—
|
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: outer Incwala | Statement: [Incwala ceremony, publicPhase, outer Incwala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicPhase Context triple: [Incwala ceremony, publicPhase, outer Incwala]
-
A.
applicationPhase
Indicates the specific stage or step an application is currently in within a broader application process.
-
B.
protocolPhase
Indicates the specific stage or step within a defined protocol or procedural sequence that an action, process, or entity is associated with.
-
C.
campaignPhase
Indicates the specific stage or period within the lifecycle of a campaign in which an entity or activity currently occurs.
-
D.
draftPhase
Indicates that an entity is currently in a preliminary or draft stage of development, not yet finalized or officially approved.
-
E.
phase
chosen
Indicates that one entity is in a particular stage, step, or phase within a process, sequence, or lifecycle relative to another reference.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328faa7448190a2606f1b37ea0a3d |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.