Triple
T19623048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBJ |
E471060
|
entity |
| Predicate | servesCruiseTourists |
P55812
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [MBJ, servesCruiseTourists, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesCruiseTourists Context triple: [MBJ, servesCruiseTourists, yes]
-
A.
servesCruisePort
chosen
Indicates that one entity (typically a transportation service or route) provides service to or operates at a particular cruise port.
-
B.
servesAttraction
Indicates that one entity functions as or provides a service that supports or enhances the experience of a particular attraction.
-
C.
servesTravelersTo
Indicates a relationship where one entity provides services, assistance, or accommodations specifically directed toward travelers heading to a particular destination.
-
D.
hasTourismFunction
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
-
E.
hasTourismResource
Indicates that a place, area, or entity possesses or is associated with a tourism-related resource, attraction, or facility.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e7949081908a89414ef899fa20 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.