Triple
T12536613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brantham |
E299706
|
entity |
| Predicate | locatedOpposite |
P3232
|
FINISHED |
| Object | Lawford |
E656597
|
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: Lawford | Statement: [Brantham, locatedOpposite, Lawford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lawford Context triple: [Brantham, locatedOpposite, Lawford]
-
A.
Lawford
Lawford is an English-origin surname most notably associated with actor Peter Lawford and, by marriage, the Kennedy political family.
-
B.
Lawford
chosen
Lawford is a village in Essex, England, situated within the scenic Dedham Vale Area of Outstanding Natural Beauty.
-
C.
Marford
Marford is a village in Wrexham County Borough, Wales, known for its distinctive Gothic-style architecture and historic character.
-
D.
Radford
Radford is a masculine given name of English origin that has been used both as a first name and surname.
-
E.
Ashford
Ashford is a small rural town in northern New South Wales, Australia, known for agriculture and its proximity to natural attractions such as caves and rivers.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9546d3b2081908d3e0659f8f13678 |
completed | April 10, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6557a95d48190ac588807544f060f |
completed | May 2, 2026, 7:50 p.m. |
Created at: April 8, 2026, 9:57 p.m.