Triple
T27168625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astwood Bank |
E682844
|
entity |
| Predicate | directionFromRedditch |
P116610
|
FINISHED |
| Object | south |
—
|
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: south | Statement: [Astwood Bank, directionFromRedditch, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromRedditch Context triple: [Astwood Bank, directionFromRedditch, south]
-
A.
hasGymLeader
Indicates that an entity (such as a location or organization) has a specific gym leader associated with it as its primary trainer or authority figure.
-
B.
WestStartingGuard
Indicates that an entity serves as the starting guard for a team representing the Western side (e.g., in an all-star or conference-based matchup).
-
C.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
D.
directionFromWarren
chosen
Indicates the relative compass direction of one location as measured outward from a reference point called Warren.
-
E.
directionType
Indicates the specific kind or category of direction associated with a movement, orientation, or relation between entities.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 9:22 a.m.