Triple
T3546155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mill City |
E75000
|
entity |
| Predicate | identityAspectOf |
P4294
|
FINISHED |
| Object | Minneapolis’s historical branding |
—
|
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: Minneapolis’s historical branding | Statement: [Mill City, identityAspectOf, Minneapolis’s historical branding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identityAspectOf Context triple: [Mill City, identityAspectOf, Minneapolis’s historical branding]
-
A.
identityConcept
Indicates that two concepts are the same in identity, representing exactly the same underlying idea or meaning.
-
B.
subjectIdentity
Indicates that two or more references correspond to the same underlying entity or individual identity.
-
C.
identityCategory
Indicates that an entity belongs to, or is classified under, a particular identity-based category or group.
-
D.
identityComponent
chosen
Indicates that one entity functions as an identifying or defining part of another entity, contributing to its overall identity.
-
E.
identificationScope
Indicates the contextual boundary or extent within which an entity is uniquely identified or recognized.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfcf64488190af8452308734028c |
completed | March 8, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69adae15749881909b847c6ca73c934e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.