Triple
T35310311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rubiera |
E1019751
|
entity |
| Predicate | railOrRoadAxis |
P127142
|
FINISHED |
| Object | between Reggio Emilia and Modena |
—
|
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: between Reggio Emilia and Modena | Statement: [Rubiera, railOrRoadAxis, between Reggio Emilia and Modena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railOrRoadAxis Context triple: [Rubiera, railOrRoadAxis, between Reggio Emilia and Modena]
-
A.
roadAxis
chosen
Indicates a central reference line that defines the primary longitudinal direction or alignment of a road.
-
B.
coordinatesRailTrafficWith
Indicates that one entity organizes and synchronizes rail operations or movements with another entity to ensure coordinated train traffic.
-
C.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
D.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
-
E.
railwayRunsAlong
Indicates that a railway line extends parallel to and in close proximity with another feature or route for a significant distance.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7905415488190bb8114e5373b862f |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.