Triple
T23581783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celebrity Cruises |
E582223
|
entity |
| Predicate | operatesVessel |
P13018
|
FINISHED |
| Object |
Celebrity Beyond
Celebrity Beyond is a modern, premium Edge-class cruise ship in the Celebrity Cruises fleet, known for its upscale amenities and contemporary design.
|
E1594511
|
NE 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: Celebrity Beyond | Statement: [Celebrity Cruises, operatesVessel, Celebrity Beyond]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Celebrity Beyond Triple: [Celebrity Cruises, operatesVessel, Celebrity Beyond]
Generated description
Celebrity Beyond is a modern, premium Edge-class cruise ship in the Celebrity Cruises fleet, known for its upscale amenities and contemporary design.
Provenance (5 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b02cf4e0819094ff4e406cda270d |
completed | April 29, 2026, 7:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0f457566b48190890b94fc14413509 |
completed | May 21, 2026, 5:48 p.m. |
| NEDg | Description generation | batch_6a0f46d5885c819098231e2178e6606e |
completed | May 21, 2026, 5:54 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0f47b410e8819093c7578df50bd669 |
completed | May 21, 2026, 5:58 p.m. |
Created at: April 17, 2026, 6:40 p.m.