Triple
T36556996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastfarthing |
E901722
|
entity |
| Predicate | hasDirectionWithinShire |
P162116
|
FINISHED |
| Object | eastern |
—
|
LITERAL 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: eastern | Statement: [Eastfarthing, hasDirectionWithinShire, eastern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionWithinShire Context triple: [Eastfarthing, hasDirectionWithinShire, eastern]
-
A.
directionFromShire
Indicates the relative compass direction of one place or object as measured outward from the Shire.
-
B.
geographicalDirectionWithinCounty
chosen
Indicates that one location lies in a specified cardinal or intercardinal direction relative to another location within the same county.
-
C.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
D.
hasApproximateDirectionFromCorkCity
Indicates that one place is located in a roughly specified compass direction when viewed from Cork City.
-
E.
directionWithinRegion
Indicates that a specified direction or heading is located entirely inside the boundaries of a given geographic or spatial region.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
Created at: May 3, 2026, 4:11 p.m.