Triple
T26214462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volow |
E655581
|
entity |
| Predicate | highlyDivergentFrom |
P6335
|
FINISHED |
| Object | Mwotlap |
—
|
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: Mwotlap | Statement: [Volow, highlyDivergentFrom, Mwotlap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highlyDivergentFrom Context triple: [Volow, highlyDivergentFrom, Mwotlap]
-
A.
followsInDivergence
Indicates that one entity comes after another specifically within a divergent or branching sequence, path, or process.
-
B.
divergenceCause
Indicates that one entity is the cause or source of a divergence, difference, or deviation observed in another entity or process.
-
C.
differentiatedFrom
chosen
Indicates that one entity is distinguished or set apart from another by identifying differences between them.
-
D.
oftenContrastedWith
Indicates that one entity is frequently compared to another in a way that highlights their differences or opposing characteristics.
-
E.
divertedFrom
Indicates that something has been redirected or rerouted away from its original or intended course, destination, or target.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d19d4648190bbee8ebc67164e60 |
completed | May 2, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:53 p.m.