Triple
T15022538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rukban camp |
E378120
|
entity |
| Predicate | peakPopulationEstimate |
P3412
|
FINISHED |
| Object | 70000 |
—
|
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: 70000 | Statement: [Rukban camp, peakPopulationEstimate, 70000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakPopulationEstimate Context triple: [Rukban camp, peakPopulationEstimate, 70000]
-
A.
peakPopulationApproximate
Indicates that the peak population of an entity is known only approximately rather than as an exact value.
-
B.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
-
C.
permanentPopulation
Indicates that an entity has a stable, long-term resident population rather than a temporary or transient presence.
-
D.
currentPopulation
Indicates the present number of individuals living in or belonging to a specified entity (such as a location or group).
-
E.
hasPopulationApproximate
chosen
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded765462c819097f331c9b39c80e3 |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a67cbc481909c19c2de57de4eb7 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 2:56 a.m.