Triple
T1305521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RYR |
E27866
|
entity |
| Predicate | primaryGeographicFocus |
P1103
|
FINISHED |
| Object | intra-European routes |
—
|
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: intra-European routes | Statement: [RYR, primaryGeographicFocus, intra-European routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryGeographicFocus Context triple: [RYR, primaryGeographicFocus, intra-European routes]
-
A.
primaryArea
Indicates that one entity is the main or most important area, domain, or field associated with another entity.
-
B.
primaryHubFor
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
-
C.
primaryTerritory
chosen
Indicates that a specified area or region is the main or most important territory associated with an entity.
-
D.
primaryVenueFor
Indicates that one entity serves as the main or principal venue or location for events, activities, or operations associated with another entity.
-
E.
primaryTopicOf
Indicates that a given subject is the main or central topic described by another resource (such as a document, page, or record).
- 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c13524d481909e8f5bb2ab91f6e4 |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4bee8544c8190874efd9bae9bccf9 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.