Triple
T33240593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | guardians of the Shire |
E850951
|
entity |
| Predicate | hasBaseNear |
P26804
|
FINISHED |
| Object | the borders of the Shire |
—
|
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: the borders of the Shire | Statement: [guardians of the Shire, hasBaseNear, the borders of the Shire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseNear Context triple: [guardians of the Shire, hasBaseNear, the borders of the Shire]
-
A.
hasNearbyBase
chosen
Indicates that one entity has a base or facility located in close physical proximity to another entity or location.
-
B.
hasNeighborhoodBase
Indicates that one topological space has a specified collection of neighborhoods at each point that forms a neighborhood base for its topology.
-
C.
hasBaseOn
Indicates that one entity is supported by, rests upon, or is structurally or conceptually founded on another entity.
-
D.
hasReserveNear
Indicates that one entity possesses or is associated with a reserve (such as a backup resource, stock, or capacity) located in close spatial proximity to another entity.
-
E.
hasStationNear
Indicates that one entity has a station located in close proximity to another entity.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 1, 2026, 1:31 a.m.