Triple
T4083520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Chase, Maine |
E87533
|
entity |
| Predicate | isPartOf |
P10
|
FINISHED |
| Object | state of Maine |
E29256
|
NE 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: state of Maine | Statement: [Mount Chase, Maine, isPartOf, state of Maine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: state of Maine Context triple: [Mount Chase, Maine, isPartOf, state of Maine]
-
A.
Maine
chosen
Maine is a northeastern U.S. state known for its rugged coastline, maritime history, and vast forested interior.
-
B.
Maine
Maine is a historical region in northwestern France that played a significant role in the medieval power struggles between the English and French crowns.
-
C.
County of Maine
The County of Maine was a medieval feudal territory in western France that became a key strategic possession contested by the counts of Anjou and the Norman and English kings.
-
D.
Freedom, Maine
Freedom, Maine is a small rural town in central Maine known for its scenic countryside and tight-knit community.
-
E.
Province of Maine
The Province of Maine was an early English colonial territory in northeastern North America that later became part of the U.S. state of Maine.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc7933b481909bb3e02c6c04c8ee |
completed | March 9, 2026, 4:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b6371762c08190ab0b829777e62540 |
completed | March 15, 2026, 4:35 a.m. |
Created at: March 9, 2026, 3:39 p.m.