Triple
T24190981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | regional train line RE1 |
E599694
|
entity |
| Predicate | operatesOnAxis |
P56811
|
FINISHED |
| Object | east–west |
—
|
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: east–west | Statement: [regional train line RE1, operatesOnAxis, east–west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesOnAxis Context triple: [regional train line RE1, operatesOnAxis, east–west]
-
A.
isOnAxis
Indicates that one entity lies directly along a specified axis or reference line defined by another entity or coordinate system.
-
B.
usesAxis
Indicates that one entity employs or relies on another entity as a reference axis or basis for orientation, measurement, or organization.
-
C.
formsAxisOf
Indicates that one entity serves together with another as the central line or primary axis around which a structure, system, or configuration is organized.
-
D.
axisWith
Indicates that one entity serves as or lies along a principal axis in relation to another entity.
-
E.
transportAxis
chosen
Indicates a directional path or axis along which something is transported or moved from one location to another.
- 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_69e288cdc8b88190bf2f835d3cb4ca28 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:35 p.m.