Triple
T10367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English |
E211
|
entity |
| Predicate | hasApproximateTotalSpeakers |
P1247
|
FINISHED |
| Object | over 1.4 billion |
—
|
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: over 1.4 billion | Statement: [English, hasApproximateTotalSpeakers, over 1.4 billion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateTotalSpeakers Context triple: [English, hasApproximateTotalSpeakers, over 1.4 billion]
-
A.
staffIncluded
Indicates that staff members are included or provided as part of the associated entity, service, or arrangement.
-
B.
hasNotableMember
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
-
C.
hasElectoralVotes
Indicates that a political entity (such as a state or district) possesses a specified number of votes in an electoral system used to choose an officeholder.
-
D.
visitorCount
Indicates the number of visitors associated with a particular entity, context, or time period.
-
E.
presentedBy
Indicates that something (such as an event, performance, or work) is formally organized, hosted, or introduced by a particular person or entity.
- 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a242cd8fb481909562f114f4ce7700 |
completed | Feb. 28, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69a23fe6b0bc8190bcce9b74f2c5fb08 |
completed | Feb. 28, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69a242cce40481908e5eae0c94313c25 |
completed | Feb. 28, 2026, 1:20 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.