Triple
T3057366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merrillville, Indiana |
E60512
|
entity |
| Predicate | metropolitanDivision |
P294
|
FINISHED |
| Object | Gary metropolitan division |
—
|
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: Gary metropolitan division | Statement: [Merrillville, Indiana, metropolitanDivision, Gary metropolitan division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metropolitanDivision Context triple: [Merrillville, Indiana, metropolitanDivision, Gary metropolitan division]
-
A.
majorDistrict
Indicates that one administrative district is the primary or most significant district associated with another entity or area.
-
B.
metropolitanOf
Indicates that one place serves as the primary metropolitan center or core urban area for another place or region.
-
C.
partOfMetropolitanArea
chosen
Indicates that one place is included within and belongs to the larger metropolitan area of another place.
-
D.
regionOfCity
Indicates that a specified area or district is a constituent part or subdivision of a particular city.
-
E.
targetCityDistrict
Indicates that one entity is a specific city district that serves as the target or destination in relation to another entity.
- 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9e162d148190969fb422a45d052c |
completed | March 8, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ad962326e081909d5521c3d3ea3158 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.