Triple
T15477383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kewevkapaya dialect |
E376817
|
entity |
| Predicate | formsContinuumWith |
P111217
|
FINISHED |
| Object | Wipukpa dialect |
—
|
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: Wipukpa dialect | Statement: [Kewevkapaya dialect, formsContinuumWith, Wipukpa dialect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsContinuumWith Context triple: [Kewevkapaya dialect, formsContinuumWith, Wipukpa dialect]
-
A.
formsWith
Indicates that one entity combines or associates with another to create or constitute a joint structure, group, or configuration.
-
B.
continuityFrom
Indicates that one entity continues, extends, or proceeds directly from another in a seamless or unbroken manner.
-
C.
formsIn
Indicates that one entity takes shape, develops, or comes into existence within or inside another entity.
-
D.
formsNear
Indicates that one entity takes shape or comes into existence in close spatial proximity to another entity.
-
E.
sharesContinuityWith
chosen
Indicates that two entities are connected through an unbroken sequence or consistent progression, such that one continues, extends, or maintains the narrative, timeline, or state established by the other.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f88a5dc8190a2d7830748e29180 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:34 a.m.