Triple
T18975966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duronto Express |
E464296
|
entity |
| Predicate | stoppingPattern |
P102636
|
FINISHED |
| Object | non-stop between origin and destination |
—
|
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: non-stop between origin and destination | Statement: [Duronto Express, stoppingPattern, non-stop between origin and destination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stoppingPattern Context triple: [Duronto Express, stoppingPattern, non-stop between origin and destination]
-
A.
stopsPattern
Indicates that one entity halts, interrupts, or prevents the continuation of a recurring or structured pattern involving another entity.
-
B.
typicalStopPattern
chosen
Indicates the usual or most common sequence or arrangement of stops associated with an entity’s operation or route.
-
C.
stoppedBy
Indicates that one entity causes another entity to cease moving, operating, or continuing an action.
-
D.
relativeStopPatternComparedTo
Indicates how one stop pattern is positioned or structured in relation to another stop pattern for comparison purposes.
-
E.
stopPolicy
Indicates that an entity terminates, cancels, or brings to an end a policy or ongoing course of action.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d61f96c88190b9a25158e0b012ca |
completed | April 20, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon