Triple
T9431361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los trabajos de Persiles y Sigismunda |
E227381
|
entity |
| Predicate | settingRoute |
P88869
|
FINISHED |
| Object | from northern Europe to Rome |
—
|
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: from northern Europe to Rome | Statement: [Los trabajos de Persiles y Sigismunda, settingRoute, from northern Europe to Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingRoute Context triple: [Los trabajos de Persiles y Sigismunda, settingRoute, from northern Europe to Rome]
-
A.
routeSetting
Indicates that one entity configures or defines the path or course to be followed by another entity (such as a vehicle, signal, or data flow).
-
B.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
C.
serviceRoute
Indicates that a service (such as a transport or delivery operation) follows or is assigned to a particular route.
-
D.
routeVia
Indicates that a connection, path, or communication between two points is established or carried out through an intermediate location, node, or channel.
-
E.
exportRoute
Indicates the route or pathway through which goods, services, or data are exported from one location or entity to another.
- F. None of above. chosen
Provenance (4 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e6059bc8190a7e98aef3caabd0b |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:49 p.m.