Triple
T8481074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MV Walla Walla |
E200518
|
entity |
| Predicate | hasPassengerDecks |
P82659
|
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: [MV Walla Walla, hasPassengerDecks, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPassengerDecks Context triple: [MV Walla Walla, hasPassengerDecks, yes]
-
A.
hasDeckType
Indicates that an entity possesses or is associated with a specific type or category of deck.
-
B.
isThroughDeck
Indicates that one object passes completely through another object or surface, extending from one side to the other.
-
C.
hasLowerDeckFunction
Indicates that an entity serves a specific role or performs a designated function on the lower deck of a structure or vehicle.
-
D.
hasUpperDecks
chosen
Indicates that one entity possesses or includes one or more upper-level decks as part of its structure.
-
E.
hasNumberOfCards
Indicates that an entity is associated with a specific quantity of cards.
- 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5245034819088c7c5c40170c020 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.