Triple
T1654557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edge Lane tram stop |
E35767
|
entity |
| Predicate | hasRealTimeInformation |
P30947
|
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: [Edge Lane tram stop, hasRealTimeInformation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRealTimeInformation Context triple: [Edge Lane tram stop, hasRealTimeInformation, yes]
-
A.
isCalculatedInRealTime
Indicates that the value or result is computed dynamically at the moment of use rather than being precomputed or stored.
-
B.
hasInformationService
Indicates that one entity provides, operates, or is associated with an information-related service for another entity.
-
C.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
D.
realityStatus
Indicates the relationship between an entity and its state of existence or authenticity within a given context or world (e.g., real, fictional, hypothetical, simulated).
-
E.
hasFareControlIntegrationSince
Indicates that a fare control system has been integrated with another system or entity starting from a specific point in time.
- 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69a907cff53c8190b424f088478d3e2c |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a99a4c3810819089d2dd0e23c8e46b |
completed | March 5, 2026, 2:59 p.m. |
Created at: March 4, 2026, 7:29 p.m.