Triple
T38044700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AIDA Cruises |
E949584
|
entity |
| Predicate | hasOnboardConcept |
P36407
|
FINISHED |
| Object | club ship concept |
—
|
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: club ship concept | Statement: [AIDA Cruises, hasOnboardConcept, club ship concept]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnboardConcept Context triple: [AIDA Cruises, hasOnboardConcept, club ship concept]
-
A.
hasOnboardFunction
Indicates that an entity includes or supports a particular function internally as part of its built-in capabilities.
-
B.
hasOnboardFeature
chosen
Indicates that an entity includes or is equipped with a particular feature as part of its built-in or onboard capabilities.
-
C.
hasOnboardButton
Indicates that one entity is equipped with or includes a button installed on or within it.
-
D.
onboarding
Indicates the process by which an entity is introduced, integrated, and given the necessary resources or information to begin participating in or using another entity (such as a system, organization, or service).
-
E.
hasOnboardSwitch
Indicates that one entity is equipped with a built-in switch located on or within it.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 3, 2026, 4:20 p.m.