Triple
T30354330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Re |
E772103
|
entity |
| Predicate | journeyPattern |
P50789
|
FINISHED |
| Object | travels across the sky by day |
—
|
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: travels across the sky by day | Statement: [Re, journeyPattern, travels across the sky by day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: journeyPattern Context triple: [Re, journeyPattern, travels across the sky by day]
-
A.
travelPattern
chosen
Indicates the typical routes, frequencies, and behaviors associated with how an entity moves or travels between locations.
-
B.
tourPattern
Indicates a recurring or structured sequence of visits or stops that defines how a tour is organized or carried out.
-
C.
plannedRailService
Indicates that a rail transport service is scheduled or intended to operate, but is not yet active or running in practice.
-
D.
transportSegment
Indicates a distinct portion of a larger journey or route during which something or someone is transported from one point to another.
-
E.
usedForRailwayTimetables
Indicates that something is employed in the creation, organization, or presentation of railway timetables.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6823cc2488190a733687581ca88a1 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 7:56 p.m.