Triple
T37391505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottumwa micropolitan area |
E928722
|
entity |
| Predicate | hasCoreBasedOn |
P67892
|
FINISHED |
| Object | Ottumwa, Iowa |
E272276
|
NE 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: Ottumwa, Iowa | Statement: [Ottumwa micropolitan area, hasCoreBasedOn, Ottumwa, Iowa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreBasedOn Context triple: [Ottumwa micropolitan area, hasCoreBasedOn, Ottumwa, Iowa]
-
A.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
B.
coreBasedOn
chosen
Indicates that one entity is fundamentally derived from, built upon, or primarily based on another entity.
-
C.
hasCoreUnit
Indicates that an entity includes or is composed around a primary, central, or fundamental unit.
-
D.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
-
E.
hasCoreArea
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
- F. None of above.
Provenance (4 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40951fea748190a5fc795dc7479ff4 |
completed | June 28, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.