Triple
T30733907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royston |
E782493
|
entity |
| Predicate | directionFromCourtenay |
P191585
|
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: [Royston, directionFromCourtenay, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromCourtenay Context triple: [Royston, directionFromCourtenay, south]
-
A.
directionFromOttawa
Indicates the cardinal or relative compass direction in which one entity is located from Ottawa.
-
B.
directionFromFlindersStreet
Indicates the compass direction or bearing of an entity when measured from Flinders Street as the point of reference.
-
C.
directionFromEdmonton
Indicates the compass direction or relative bearing of one place or object as measured outward from Edmonton.
-
D.
roadDirectionFromCanada
Indicates the direction in which a road extends or leads when traveling outward from Canada toward another location.
-
E.
directionFromRyde
Indicates the compass direction or relative bearing of one location or object measured from the reference point Ryde.
- F. None of above. chosen
Provenance (4 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:37 p.m.