Triple
T30562917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis–St. Charles–Farmington, MO–IL combined statistical area |
E777893
|
entity |
| Predicate | isBiStateArea |
P152129
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [St. Louis–St. Charles–Farmington, MO–IL combined statistical area, isBiStateArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBiStateArea Context triple: [St. Louis–St. Charles–Farmington, MO–IL combined statistical area, isBiStateArea, true]
-
A.
isMultiState
chosen
Indicates that the entity exists or operates in more than one distinct state or condition.
-
B.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with another entity.
-
C.
isSupplementaryArea
Indicates that one area serves as an additional or supporting area to another primary area within a given context.
-
D.
isPartOfCombinedArea
Indicates that an entity belongs to or is included within a larger merged or aggregated area.
-
E.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
- 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_69f2249ed41c8190b175170ecfd6e1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f688d9f1f08190b9f844ad98531cdb |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:21 p.m.