Triple
T36556778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Far Downs |
E901717
|
entity |
| Predicate | marksOuterReachesOf |
P49185
|
FINISHED |
| Object | the Shire |
—
|
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: the Shire | Statement: [The Far Downs, marksOuterReachesOf, the Shire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksOuterReachesOf Context triple: [The Far Downs, marksOuterReachesOf, the Shire]
-
A.
marksBoundaryIn
chosen
Indicates that one entity serves as a boundary or delimiter within, or for a specific region or structure of, another entity.
-
B.
marksLocationOf
Indicates that one entity serves as a marker, sign, or indicator specifying the location of another entity.
-
C.
marksApproachTo
Indicates that one entity signifies or designates the way or method by which another entity is approached.
-
D.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
E.
reaches
Indicates that one entity extends or moves until it makes contact with, attains, or arrives at another entity or point.
- 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_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.