Triple
T199427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arab League |
E4067
|
entity |
| Predicate | populationOfMemberStatesApprox |
P3412
|
FINISHED |
| Object | over 400 million |
—
|
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 400 million | Statement: [Arab League, populationOfMemberStatesApprox, over 400 million]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationOfMemberStatesApprox Context triple: [Arab League, populationOfMemberStatesApprox, over 400 million]
-
A.
demographicScope
Indicates the specific population group or demographic segment to which something (e.g., a policy, study, product, or service) is targeted or applicable.
-
B.
hasPopulationApproximate
chosen
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
C.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
-
D.
hasPopulationRank
Indicates the relative position of an entity in an ordered list based on the size of its population.
-
E.
populationDensity
Indicates the number of individuals or entities occupying a unit area within a given region.
- 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_69a254bca59881909a15e1496f1508c7 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25bcc6dc88190b8c24b485588dfe4 |
completed | Feb. 28, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69a25b4886b48190b46fd2244648a098 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:44 a.m.