Triple
T2247421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marham Abbey |
E49536
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Marham |
E49536
|
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: Marham | Statement: [Marham Abbey, locatedIn, Marham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Marham Context triple: [Marham Abbey, locatedIn, Marham]
-
A.
Marham
chosen
Marham is a village in Norfolk, England, best known for hosting RAF Marham, a major Royal Air Force station.
-
B.
Shouldham
Shouldham is a small rural village in Norfolk, England, known for its traditional English countryside setting and historic character.
-
C.
Issoudun
Issoudun is a historic commune in central France known for its medieval architecture and location within the Indre department.
-
D.
Al Quoz
Al Quoz is an industrial and residential district in western Dubai known for its warehouses, factories, and growing arts and cultural scene.
-
E.
Bahraich
Bahraich is a city in the Indian state of Uttar Pradesh, known for its location in the Terai region near the Nepal border and its historical and cultural significance.
- 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_69a88aa979788190ad6500f1d8eee2fc |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0ec46b08190ae12de8b255eb71d |
completed | March 7, 2026, 6:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae71c1edd081909acbb8b1915ce0d6 |
completed | March 9, 2026, 7:07 a.m. |
Created at: March 4, 2026, 7:47 p.m.