Triple
T34037770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lochmoor |
E872853
|
entity |
| Predicate | usedAsMunicipalNameFor |
P99228
|
FINISHED |
| Object | suburban community northeast of Detroit |
—
|
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: suburban community northeast of Detroit | Statement: [Lochmoor, usedAsMunicipalNameFor, suburban community northeast of Detroit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsMunicipalNameFor Context triple: [Lochmoor, usedAsMunicipalNameFor, suburban community northeast of Detroit]
-
A.
usedAsTownNameFor
chosen
Indicates that something serves as the official or common name of a particular town.
-
B.
usedAsToponymicBy
Indicates that one entity is employed as a place-based surname or name-forming element for another entity.
-
C.
usedAsTownNameUntil
Indicates that an entity served as the official or common name of a town up to a specified point in time.
-
D.
municipalityName
Indicates the official name assigned to a municipality.
-
E.
usedAsNamesakeFor
Indicates that one entity serves as the source or inspiration for the name given 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 1, 2026, 1:51 a.m.