Triple
T24472089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vovo |
E617126
|
entity |
| Predicate | spokenInProximityTo |
P67236
|
FINISHED |
| Object | Nese language |
—
|
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: Nese language | Statement: [Vovo, spokenInProximityTo, Nese language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokenInProximityTo Context triple: [Vovo, spokenInProximityTo, Nese language]
-
A.
spokenNear
Indicates that one entity spoke in close physical proximity to another entity or location.
-
B.
isSpokenAround
chosen
Indicates that something (such as a language, phrase, or expression) is commonly spoken in the vicinity of, or within the general area surrounding, a particular place or entity.
-
C.
spokenInLocality
Indicates that a language, dialect, or speech form is used or spoken within a specific locality or geographic area.
-
D.
speaksWith
Indicates that one entity engages in spoken communication or conversation with another entity.
-
E.
spokeAt
Indicates that a person delivered a talk, speech, or presentation at a particular event or location.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29943e9cc81909f1742c778bf3587 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:20 a.m.