Triple
T24262682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Showboat Branson Belle |
E604749
|
entity |
| Predicate | cruiseLocation |
P110322
|
FINISHED |
| Object | Table Rock Lake |
—
|
NE NERFINISHED |
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: Table Rock Lake | Statement: [Showboat Branson Belle, cruiseLocation, Table Rock Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cruiseLocation Context triple: [Showboat Branson Belle, cruiseLocation, Table Rock Lake]
-
A.
cruiseRegion
Indicates the geographic region or area in which a cruise operates or takes place.
-
B.
endPointOfPopularCruise
Indicates that a location serves as a final destination or stopping point for a popular cruise route.
-
C.
locationDuringCruise
chosen
Indicates that an entity’s location is specified for the duration of a cruise or while a cruise is taking place.
-
D.
isCruisePort
Indicates that a location functions as a port where cruise ships dock, embark, or disembark passengers.
-
E.
servesCruisePort
Indicates that one entity (typically a transportation service or route) provides service to or operates at a particular cruise port.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c691eb08190b6fbda8f187d7427 |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:06 a.m.