Triple
T6879359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ME |
E158750
|
entity |
| Predicate | distinctFrom |
P1612
|
FINISHED |
| Object | ISO 3166-2:US-ME |
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: ISO 3166-2:US-ME | Statement: [ME, distinctFrom, ISO 3166-2:US-ME]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISO 3166-2:US-ME Context triple: [ME, distinctFrom, ISO 3166-2:US-ME]
-
A.
ISO 3166-2:US
ISO 3166-2:US is the section of the ISO 3166 standard that defines internationally recognized subdivision codes for the states and territories of the United States.
-
B.
Maine
chosen
Maine is a northeastern U.S. state known for its rugged coastline, maritime history, and vast forested interior.
-
C.
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.
-
D.
Mexico, Maine
Mexico, Maine is a small town in Oxford County known historically as a mill and residential community closely linked with the neighboring industrial town of Rumford.
-
E.
Maryland
Maryland is a Mid-Atlantic U.S. state known for its Chesapeake Bay shoreline, colonial history, and proximity to the nation’s capital.
- 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_69c68832af1481908ce356e133ebaebe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8e60f94819086315b1dd2ea7a3e |
completed | March 27, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c742c2b81881909bd13df0d6028cc6 |
completed | March 28, 2026, 2:53 a.m. |
Created at: March 27, 2026, 2:22 p.m.