Triple
T499693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mesopotamian Arabic |
E10372
|
entity |
| Predicate | hasSpeakers |
P1247
|
FINISHED |
| Object | millions of speakers |
—
|
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: millions of speakers | Statement: [Mesopotamian Arabic, hasSpeakers, millions of speakers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeakers Context triple: [Mesopotamian Arabic, hasSpeakers, millions of speakers]
-
A.
hasMainSpeaker
Indicates that one entity serves as the primary or principal speaker associated with another entity, such as an event, recording, or presentation.
-
B.
hasApproximateTotalSpeakers
chosen
Indicates that an entity is associated with an estimated or roughly calculated number of total speakers, rather than an exact count.
-
C.
hasNativeSpeakers
Indicates that a language or dialect is spoken as a first language by one or more people or populations.
-
D.
spokeAt
Indicates that a person delivered a talk, speech, or presentation at a particular event or location.
-
E.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f119b14c8190a5a6b119579c2682 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edfa87cc8190a77c726a5a55b7d9 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.