Triple
T26733138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberty Belle riverboat cruises |
E674027
|
entity |
| Predicate | boatDecks |
P81629
|
FINISHED |
| Object | multiple passenger decks |
—
|
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: multiple passenger decks | Statement: [Liberty Belle riverboat cruises, boatDecks, multiple passenger decks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boatDecks Context triple: [Liberty Belle riverboat cruises, boatDecks, multiple passenger decks]
-
A.
gunDecks
Indicates that one entity is equipped with, contains, or is associated with the gun decks of another entity, typically referring to the levels or platforms on a vessel where guns are mounted.
-
B.
boatConfiguration
chosen
Indicates the specific arrangement, layout, or setup of components or features on a boat.
-
C.
boatPower
Indicates a relationship where a boat is characterized by or associated with a specific power rating or propulsion strength.
-
D.
boatStudio
Indicates a relationship where a boat is associated with, produced by, or represented by a particular studio or production company.
-
E.
boatDecorationStyle
Indicates the stylistic theme or manner in which a boat is decorated.
- 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f618429e9481908140bb49a3edd6de |
completed | May 2, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:46 a.m.