Triple
T37507753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Idyllia |
E932140
|
entity |
| Predicate | travelHubRole |
P137851
|
FINISHED |
| Object | support area within Oribos |
—
|
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: support area within Oribos | Statement: [The Idyllia, travelHubRole, support area within Oribos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelHubRole Context triple: [The Idyllia, travelHubRole, support area within Oribos]
-
A.
travelRole
Indicates the specific role or capacity an entity has in relation to a travel activity or journey (e.g., traveler, guide, driver).
-
B.
travelRouteRole
chosen
Indicates the specific functional role an entity plays within a travel route, such as origin, destination, or intermediate stop.
-
C.
travelHub
Indicates a location that serves as a central node or major interchange point for travel or transportation connections between different places or routes.
-
D.
coTraveler
Indicates that two or more entities are traveling together along (part of) the same journey or route.
-
E.
travelMechanic
Indicates the method or system by which movement or travel between locations is carried out.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.