Triple
T18124945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windsor, Maine |
E433845
|
entity |
| Predicate | isPartOfMetaregion |
P92567
|
FINISHED |
| Object | rural central Maine |
—
|
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: rural central Maine | Statement: [Windsor, Maine, isPartOfMetaregion, rural central Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfMetaregion Context triple: [Windsor, Maine, isPartOfMetaregion, rural central Maine]
-
A.
locatedInMetaregion
chosen
Indicates that one entity is geographically or administratively situated within a larger metaregion.
-
B.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
C.
belongsToMetropolitanRegion
Indicates that one geographic or administrative area is part of, or included within, a larger metropolitan region.
-
D.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with another entity.
-
E.
isInSubregion
Indicates that one region or area is located within the boundaries of another, more specific subregion.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dded1bd4819080fa362e88c921cf |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.