Triple
T1769985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newport, Maine |
E38851
|
entity |
| Predicate | hasRegionRole |
P12921
|
FINISHED |
| Object | regional service center |
—
|
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: regional service center | Statement: [Newport, Maine, hasRegionRole, regional service center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionRole Context triple: [Newport, Maine, hasRegionRole, regional service center]
-
A.
hasRegionalRole
chosen
Indicates that an entity holds a specific role, function, or responsibility within a defined geographic region.
-
B.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
C.
hasRegionalIdentity
Indicates that an entity possesses or is associated with a specific regional or local identity.
-
D.
eligibleRegion
Indicates the geographic area within which something (such as an offer, service, or rule) is valid, applicable, or permitted.
-
E.
isKeyRegionFor
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.