Triple
T27199153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moro languages |
E683686
|
entity |
| Predicate | haveSpeakersWhoAre |
P162245
|
FINISHED |
| Object | predominantly Muslim |
—
|
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: predominantly Muslim | Statement: [Moro languages, haveSpeakersWhoAre, predominantly Muslim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveSpeakersWhoAre Context triple: [Moro languages, haveSpeakersWhoAre, predominantly Muslim]
-
A.
hasSpeakersAmong
Indicates that a group, event, or entity includes one or more speakers drawn from a specified set or category.
-
B.
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.
-
C.
hasSpeakersAlong
Indicates that something is equipped with or accompanied by speakers positioned along its length or path.
-
D.
hasSpeakersType
Indicates that an entity has speakers of a specified type or category.
-
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_69eefad1fd5c8190a4a46ea6afe58bfa |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625dea3788190a97467cc8e613a12 |
completed | May 2, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 9:35 a.m.