Triple
T31412322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Louis Bread Company |
E801299
|
entity |
| Predicate | usesNameInRegion |
P40944
|
FINISHED |
| Object | St. Louis metropolitan area |
—
|
NE NERFINISHED |
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: St. Louis metropolitan area | Statement: [St. Louis Bread Company, usesNameInRegion, St. Louis metropolitan area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNameInRegion Context triple: [St. Louis Bread Company, usesNameInRegion, St. Louis metropolitan area]
-
A.
regionNameUsedFor
Indicates that a particular region name is used to refer to or designate a specific region or area.
-
B.
hasRegionalName
chosen
Indicates that an entity is known by a specific name or designation within a particular region or locality.
-
C.
usesNameDueTo
Indicates that one entity adopts or applies a particular name for another entity specifically because of some motivating reason, circumstance, or dependency.
-
D.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
-
E.
usedInRegion
Indicates that something is utilized or applied within a specific geographic or administrative region.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:39 p.m.