Triple
T19465710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock Region METRO streetcar |
E486990
|
entity |
| Predicate | isElectricTransit |
P10917
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Rock Region METRO streetcar, isElectricTransit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isElectricTransit Context triple: [Rock Region METRO streetcar, isElectricTransit, true]
-
A.
isElectricRailway
chosen
Indicates that a given railway system operates using electric power rather than diesel or other forms of propulsion.
-
B.
isPublicTransport
Indicates that the entity functions as a mode or instance of transportation that is available for use by the general public, typically operating on fixed routes or schedules.
-
C.
isPublicTransportIn
Indicates that a mode or instance of public transportation operates within, serves, or is located in a specified area or region.
-
D.
hasFormOfPublicTransit
Indicates that one entity provides or is associated with a particular type or mode of public transportation for another entity or context.
-
E.
hasTrolleybusSystem
Indicates that an entity operates or is served by a trolleybus transportation system.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e1dccc819096feb1a514b9eb86 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.