Triple
T20148115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innsworth |
E491360
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Gloucester |
—
|
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: Gloucester | Statement: [Innsworth, near, Gloucester]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gloucester Context triple: [Innsworth, near, Gloucester]
-
A.
Gloucester
Gloucester is a historic coastal city in northeastern Massachusetts known for its long-standing fishing industry and maritime heritage.
-
B.
Gloucester
Gloucester is a rural town in New South Wales, Australia, known as a gateway to the Barrington Tops region and for its agriculture and scenic river valley setting.
-
C.
Gloucester
chosen
Gloucester is a historic cathedral city and port in southwest England, known for its medieval architecture and role as the county town of Gloucestershire.
-
D.
Glocester
Glocester is a rural town in northwestern Rhode Island known for its historic villages, woodlands, and small-town New England character.
-
E.
Gloucester City
Gloucester City is a small, historically industrial city in Camden County, New Jersey, located along the Delaware River across from Philadelphia.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667a0075c8190a5c4de53a0caa7f6 |
completed | April 20, 2026, 5:51 p.m. |
Created at: April 11, 2026, 11:33 p.m.