Triple
T14948788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utoro |
E372735
|
entity |
| Predicate | hasTransportServiceType |
P849
|
FINISHED |
| Object | sightseeing boats |
—
|
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: sightseeing boats | Statement: [Utoro, hasTransportServiceType, sightseeing boats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransportServiceType Context triple: [Utoro, hasTransportServiceType, sightseeing boats]
-
A.
hasServiceType
chosen
Indicates that an entity is associated with or categorized by a particular type of service.
-
B.
hasTransportCategory
Indicates that one entity is classified under a particular category or type of transport associated with another entity.
-
C.
hasTransportCode
Indicates that an entity is associated with a specific transport-related code used to identify or classify its mode, method, or details of transportation.
-
D.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
E.
hasTugServices
Indicates that tug assistance or towing services are provided or available for a given entity or location.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded68fae3c81909873b113bfcaca05 |
completed | April 15, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:39 a.m.