Triple
T3217991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woy Woy |
E67442
|
entity |
| Predicate | directionFromGosford |
P46575
|
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: [Woy Woy, directionFromGosford, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromGosford Context triple: [Woy Woy, directionFromGosford, south]
-
A.
directionFromSydney
Indicates the compass direction or relative bearing of one location when measured outward starting from Sydney.
-
B.
directionFromCanberra
Indicates the cardinal or relative compass direction in which one location lies when measured from Canberra.
-
C.
directionFromMelbourne
Indicates the compass direction in which one entity is located relative to Melbourne.
-
D.
directionFromMildura
Indicates the compass direction or bearing of one location when measured from Mildura.
-
E.
directionFromNewcastle
Indicates the compass direction or relative bearing of one place or object when measured starting from Newcastle as the reference point.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab0c48b481909d1bd9dc41dfa8c2 |
completed | March 8, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0bb6c48190a0659c67d40ee37c |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada148e9108190b363dd0f1a94ac8e |
completed | March 8, 2026, 4:18 p.m. |
Created at: March 8, 2026, 3:08 p.m.