Triple
T8617454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond Township, Michigan |
E204075
|
entity |
| Predicate | isInUpperPeninsula |
P83917
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Richmond Township, Michigan, isInUpperPeninsula, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInUpperPeninsula Context triple: [Richmond Township, Michigan, isInUpperPeninsula, true]
-
A.
hasUpperLakes
Indicates that an entity (typically a water body or region) possesses or is associated with one or more lakes located upstream or at a higher elevation relative to it.
-
B.
isInNorthCentralPartOf
Indicates that one entity is located within the north-central region of another entity.
-
C.
isInUpstateNewYork
Indicates that a location or entity is situated within the geographic region commonly referred to as Upstate New York.
-
D.
locatedInLakeRegion
Indicates that the subject entity is situated within a geographic area characterized as a lake region.
-
E.
isInUSState
Indicates that one entity (typically a place or location) is geographically located within the boundaries of a specific U.S. state.
- 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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc4711c7748190af26ff5a78ef66a2 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:26 p.m.