Triple
T34157598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colerain Township, Hamilton County, Ohio |
E876182
|
entity |
| Predicate | directionFromCincinnati |
P195103
|
FINISHED |
| Object | northwest |
—
|
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: northwest | Statement: [Colerain Township, Hamilton County, Ohio, directionFromCincinnati, northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromCincinnati Context triple: [Colerain Township, Hamilton County, Ohio, directionFromCincinnati, northwest]
-
A.
directionFromColumbus
Indicates the compass direction in which one location lies when measured from Columbus.
-
B.
directionFromPittsburgh
Indicates the cardinal or relative compass direction in which one entity is located from Pittsburgh.
-
C.
directionFromIndianapolis
Indicates the cardinal or relative compass direction of one place or object as measured from Indianapolis.
-
D.
directionFromNashville
Indicates the cardinal or relative compass direction in which one entity is located from Nashville.
-
E.
directionFromSyracuse
Indicates the cardinal or relative direction in which one entity is located from Syracuse.
- F. None of above. chosen
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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
| PDg | Predicate description generation | batch_69fda4fe67a08190bdaa84ceabd6de6c |
completed | May 8, 2026, 8:55 a.m. |
Created at: May 1, 2026, 1:54 a.m.