Triple
T11896120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Knox (Maine) |
E283038
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Prospect, Maine |
—
|
NE NERFINISHED |
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: Prospect, Maine | Statement: [Fort Knox (Maine), locatedIn, Prospect, Maine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Prospect, Maine Context triple: [Fort Knox (Maine), locatedIn, Prospect, Maine]
-
A.
Prospect, Maine
chosen
Prospect, Maine is a small rural town in Waldo County known for its historic Fort Knox and scenic views along the Penobscot River.
-
B.
Porter, Maine
Porter, Maine is a small rural town in Oxford County known for its scenic setting near the New Hampshire border and its traditional New England character.
-
C.
Lovell, Maine
Lovell, Maine is a small rural town in Oxford County known for its scenic lakes and mountains in western Maine.
-
D.
Blaine, Maine
Blaine, Maine is a small rural town located in northeastern Maine near the Canadian border, within Aroostook County’s agricultural region.
-
E.
Thorndike, Maine
Thorndike, Maine is a small rural town located in Waldo County in the central part of the state.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8dd1286808190949719f54ff49a01 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:44 p.m.