Triple
T35475011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MI |
E1025306
|
entity |
| Predicate | associatedWithDistrictCapital |
P207000
|
FINISHED |
| Object | Minden |
E177242
|
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: Minden | Statement: [MI, associatedWithDistrictCapital, Minden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithDistrictCapital Context triple: [MI, associatedWithDistrictCapital, Minden]
-
A.
associatedWithProvinceCapital
Indicates that an entity has a relationship or connection to the capital city of a specific province.
-
B.
isInDistrictCapitalCity
Indicates that one entity is located within the capital city of a specified administrative district.
-
C.
connectsToRegionalCapital
Indicates that one location has a direct connection, such as a transport or administrative link, to a designated regional capital.
-
D.
isDistrictCapitalOf
Indicates that a location serves as the administrative or governmental capital of a specified district.
-
E.
belongsToDistrictLevelCity
Indicates that an entity is administratively part of, or falls under the jurisdiction of, a specific district-level city.
- F. None of above. chosen
Provenance (5 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3852ddd7c8819084295cf79c9a6547 |
completed | June 21, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.