Triple
T4088375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NL21 |
E87644
|
entity |
| Predicate | statisticalUnit |
P49001
|
FINISHED |
| Object | province |
—
|
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: province | Statement: [NL21, statisticalUnit, province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statisticalUnit Context triple: [NL21, statisticalUnit, province]
-
A.
statisticalUnitOf
chosen
Indicates that one entity serves as the statistical unit (the basic unit of observation or analysis) for which data or statistics are collected or reported about another entity.
-
B.
populationUnit
Indicates the unit of measurement in which a population quantity is expressed (e.g., individuals, households, families).
-
C.
samplingUnit
Indicates that one entity serves as the basic unit or element from which samples are drawn or measured in a sampling process.
-
D.
governmentalUnit
Indicates that one entity functions as a governmental or administrative unit in relation to another entity.
-
E.
administrativeTerritorialEntityOf
Indicates that one entity serves as the administrative territorial unit or jurisdiction to which another entity belongs or is governed by.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefca9e9088190a97cb2ccb5d622f0 |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.