Triple
T21053570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Segeju language |
E518649
|
entity |
| Predicate | hasSpeakersAlong |
P142652
|
FINISHED |
| Object | Indian Ocean 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: Indian Ocean coast | Statement: [Segeju language, hasSpeakersAlong, Indian Ocean coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeakersAlong Context triple: [Segeju language, hasSpeakersAlong, Indian Ocean coast]
-
A.
hasSpeakersIn
Indicates that an entity (such as an event, conference, or session) includes or is associated with speakers located in or belonging to a specified place or group.
-
B.
hasSpeakersAmong
Indicates that a group, event, or entity includes one or more speakers drawn from a specified set or category.
-
C.
hasSpeakersType
Indicates that an entity has speakers of a specified type or category.
-
D.
hasSpeakerType
Indicates that an entity functions in a particular role or category as a speaker (e.g., narrator, character, announcer) within a given context.
-
E.
speakers
Indicates that one or more entities produce spoken language or vocal communication, typically addressing an audience or participating in a conversation.
- F. None of above. chosen
Provenance (4 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd7e087c81908712ddc63e8b1e6c |
completed | April 21, 2026, 4:30 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:36 p.m.