Triple
T41692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waverley |
E822
|
entity |
| Predicate | hasAtGradeCrossingNearby |
P3381
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Waverley, hasAtGradeCrossingNearby, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAtGradeCrossingNearby Context triple: [Waverley, hasAtGradeCrossingNearby, yes]
-
A.
crossesBetween
Indicates that one entity passes from one side of a second entity to the other, traversing the space between two reference points or boundaries associated with that second entity.
-
B.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
C.
meetsAtLevel
Indicates that two or more entities encounter or interact with each other at a specific hierarchical, structural, or progression level.
-
D.
hasJunctionWith
Indicates that one entity meets or intersects with another at a shared junction point.
-
E.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
- 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24db9527c8190816b6b25c88cb2f4 |
completed | Feb. 28, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69a24ab8a8908190beec6da6694dd4c9 |
completed | Feb. 28, 2026, 1:54 a.m. |
| PDg | Predicate description generation | batch_69a24db81c748190948560892f12c61b |
completed | Feb. 28, 2026, 2:06 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.