Triple
T5335357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabaki languages |
E123812
|
entity |
| Predicate | areSpokenAlong |
P38694
|
FINISHED |
| Object | East African coast |
—
|
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: East African coast | Statement: [Sabaki languages, areSpokenAlong, East African coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areSpokenAlong Context triple: [Sabaki languages, areSpokenAlong, East African coast]
-
A.
isSpokenAlong
chosen
Indicates that something (typically a language or dialect) is used or spoken in the regions or areas that follow a particular path, boundary, or route.
-
B.
spokenAlong
Indicates that two or more languages are used concurrently or within the same context in a particular place, time, or situation.
-
C.
alsoSpeak
Indicates that an entity, in addition to another language or mode of communication already mentioned, speaks this additional language or communicates in this additional way.
-
D.
spokenOn
Indicates that an utterance or speech act occurred at or during a specific time or date.
-
E.
speaksIn
Indicates that an entity uses or expresses itself in a particular language or medium when speaking.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85af799081909ee60bfbb65149ee |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.