Triple
T546437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semitic languages |
E12741
|
entity |
| Predicate | hasLivingSpeakers |
P1247
|
FINISHED |
| Object | hundreds of millions of people |
—
|
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: hundreds of millions of people | Statement: [Semitic languages, hasLivingSpeakers, hundreds of millions of people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLivingSpeakers Context triple: [Semitic languages, hasLivingSpeakers, hundreds of millions of people]
-
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.
hasNativeSpeakers
Indicates that a language or dialect is spoken as a first language by one or more people or populations.
-
C.
hasApproximateTotalSpeakers
chosen
Indicates that an entity is associated with an estimated or roughly calculated number of total speakers, rather than an exact count.
-
D.
hasSpeech
Indicates that an entity produces, delivers, or is associated with a spoken utterance or verbal expression.
-
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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a498e150e88190b35b1bc7a376ca07 |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494b957988190bc269e372df2f0b2 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.