Triple
T18372233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenwich Steps |
E446208
|
entity |
| Predicate | hasApproximateDirection |
P40031
|
FINISHED |
| Object | east–west |
—
|
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: east–west | Statement: [Greenwich Steps, hasApproximateDirection, east–west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateDirection Context triple: [Greenwich Steps, hasApproximateDirection, east–west]
-
A.
approximateDirection
chosen
Indicates that one entity is located in a general or rough directional relation (e.g., roughly north, south, etc.) relative to another entity, without specifying an exact bearing.
-
B.
hasApproximateHeading
Indicates that one entity’s directional heading is approximately the same as another’s, within a specified tolerance.
-
C.
hasApproximateHeadingDegrees
Indicates that one entity’s heading or direction is approximately equal to a specified angle measured in degrees.
-
D.
isInDirectionOf
Indicates that one entity is oriented or positioned toward the direction in which another entity lies.
-
E.
hasApproximateOrigin
Indicates that an entity originates from a source or location that is known only approximately rather than precisely.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51754539c819083f13b85cacb6cce |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:44 a.m.