Triple
T15228960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Region IV-A |
E363946
|
entity |
| Predicate | hasStatisticalCode |
P102462
|
FINISHED |
| Object | 04-A |
—
|
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: 04-A | Statement: [Region IV-A, hasStatisticalCode, 04-A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatisticalCode Context triple: [Region IV-A, hasStatisticalCode, 04-A]
-
A.
hasStatisticalRole
Indicates that an entity participates in a context (such as a study, dataset, or analysis) with a specific statistical function or role (e.g., variable, parameter, estimator).
-
B.
hasStatistics
Indicates that an entity is associated with one or more statistical measures, records, or summaries describing its quantitative properties or performance.
-
C.
hasStatisticsAgency
Indicates that an entity is officially served or overseen by a particular statistics agency responsible for collecting and providing its statistical data.
-
D.
hasStandardCode
chosen
Indicates that an entity is associated with a recognized standard code that formally identifies or classifies it.
-
E.
statisticalType
Indicates that one entity specifies the kind or category of statistical characterization or measurement that applies to another entity.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0078ccdf48190b34eabd9e24e45a1 |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.