Triple
T293012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Kent, Maine |
E6034
|
entity |
| Predicate | state |
P87
|
FINISHED |
| Object | 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: Maine | Statement: [Fort Kent, Maine, state, Maine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maine Context triple: [Fort Kent, Maine, state, 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.
New Hampshire
New Hampshire is a small New England state in the northeastern United States known for its mountainous landscapes, early presidential primary, and “Live Free or Die” motto.
-
D.
Vermont
Vermont is a small, rural New England state in the northeastern United States, known for its Green Mountains, maple syrup production, and picturesque towns.
-
E.
Strong, Maine
Strong, Maine is a small rural town in western Maine known historically for its lumber and toothpick manufacturing industries.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2e976f32081908042485c4530e1e2 |
completed | Feb. 28, 2026, 1:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac65f5fa54819087f7d08cdaa5e5ea |
completed | March 7, 2026, 5:52 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.