Triple
T15475255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semitic peoples |
E376766
|
entity |
| Predicate | currentlySpeak |
P118396
|
FINISHED |
| Object | Arabic 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: Arabic language | Statement: [Semitic peoples, currentlySpeak, Arabic language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentlySpeak Context triple: [Semitic peoples, currentlySpeak, Arabic language]
-
A.
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.
-
B.
mainSpeechBy
Indicates that a speech or primary address is delivered or given by a particular entity.
-
C.
spokenUntil
Indicates that an act of speaking or verbal communication continues up to a specific time or event and then stops.
-
D.
givesSpeechTo
Indicates that one entity delivers a speech or formal address directed toward another entity or audience.
-
E.
hasSpeech
Indicates that an entity produces, delivers, or is associated with a spoken utterance or verbal expression.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6e859481909c3d08343b7ad27c |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded5deee00819099fa3e43313312e1 |
completed | April 15, 2026, 12:03 a.m. |
Created at: April 10, 2026, 3:34 a.m.