Triple
T26193714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Reserve Bank of Chicago |
E655035
|
entity |
| Predicate | branchLocation |
P160030
|
FINISHED |
| Object | Detroit, Michigan |
—
|
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: Detroit, Michigan | Statement: [Federal Reserve Bank of Chicago, branchLocation, Detroit, Michigan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchLocation Context triple: [Federal Reserve Bank of Chicago, branchLocation, Detroit, Michigan]
-
A.
branchPosition
Indicates the relative location or placement of something along a branch.
-
B.
branchPoint
Indicates a point in a process, structure, or path where a single preceding element splits into two or more alternative continuations or options.
-
C.
benchLocation
Indicates that a bench is located at or associated with a specific place or position.
-
D.
branchSpecific
Indicates that something is associated with, restricted to, or applicable only within a particular branch or subdivision of a larger organization or structure.
-
E.
branchNetwork
Indicates that one entity operates as a branch or local outlet within the wider organizational or operational network of another entity.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60ca4397481908a10249146f7c5ef |
completed | May 2, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8:45 p.m.