Triple
T38327402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maggotts |
E1036825
|
entity |
| Predicate | hasAdjacentCorner |
P5707
|
FINISHED |
| Object | Becketts |
—
|
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: Becketts | Statement: [Maggotts, hasAdjacentCorner, Becketts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentCorner Context triple: [Maggotts, hasAdjacentCorner, Becketts]
-
A.
hasAdjacentQuadrant
Indicates that one quadrant is directly next to another quadrant, sharing a common boundary or side.
-
B.
hasCorner
Indicates that one entity possesses or includes a corner that is part of or associated with another entity.
-
C.
isAdjacentTo
chosen
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
D.
hasCornerCount
Indicates that an entity is associated with a specific number of corners.
-
E.
hasNeighbouringQuarter
Indicates that one quarter (district or area) is directly adjacent to and shares a boundary with another quarter.
- F. None of above.
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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 3, 2026, 4:30 p.m.