Triple
T17945611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coast City |
E448693
|
entity |
| Predicate | populationBeforeDestruction |
P129836
|
FINISHED |
| Object | approximately seven 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: approximately seven million | Statement: [Coast City, populationBeforeDestruction, approximately seven million]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationBeforeDestruction Context triple: [Coast City, populationBeforeDestruction, approximately seven million]
-
A.
populationAfterDestruction
Indicates the size or composition of a population following an event of destruction or devastation.
-
B.
populationBeforeEvacuation
Indicates the number of individuals present in a specified place or group prior to an evacuation event.
-
C.
populationLoss
Indicates a decrease in the number of individuals within a defined population over a given period or due to specific causes.
-
D.
populationAfterSiege
Indicates the number of people remaining in a place after a siege has concluded.
-
E.
formerPopulation
Indicates that an entity once had a certain population value or size during a past time period but no longer does.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad990b948190a5e6fd50a15f64e3 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:21 a.m.