Triple
T27380375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randolph County, Missouri |
E691205
|
entity |
| Predicate | economicRoleOfMoberly |
P89201
|
FINISHED |
| Object | regional hub city |
—
|
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: regional hub city | Statement: [Randolph County, Missouri, economicRoleOfMoberly, regional hub city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicRoleOfMoberly Context triple: [Randolph County, Missouri, economicRoleOfMoberly, regional hub city]
-
A.
MorrisBrownOccupation
Indicates that a specified person holds or held a particular occupation or job position at Morris Brown.
-
B.
socioeconomicRole
chosen
Indicates the social and economic position, function, or status an entity holds within a society or system.
-
C.
economicRolePast
Indicates that an entity previously held a specific economic function, position, or role in the past.
-
D.
populationRankInMissouri
Indicates the relative position of an entity in terms of population size compared to other entities within the state of Missouri.
-
E.
ethnicRole
Indicates a role, function, or social position that is specifically associated with or defined by an entity’s ethnicity.
- 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_69ef52022538819081f873d0c84a6dd6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 12:22 p.m.