Triple
T15200859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castets-en-Dorthe |
E363262
|
entity |
| Predicate | populationReferenceYear |
P5555
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Castets-en-Dorthe, populationReferenceYear, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationReferenceYear Context triple: [Castets-en-Dorthe, populationReferenceYear, 2013]
-
A.
populationCensusYear
Indicates the specific year in which an official population census was conducted or recorded for an entity.
-
B.
basedOnCensusYear
Indicates that something (such as data, a decision, or a classification) is derived from or determined using information from a specific census year.
-
C.
populationAge
Indicates the age or age distribution of a population associated with an entity.
-
D.
hasPopulationAsOf
chosen
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
-
E.
populationBasis
Indicates that a population measurement is based on, derived from, or defined with respect to a particular reference, criterion, or underlying basis.
- 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b588b88190a88e91d521acbdfe |
completed | April 15, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:10 a.m.