Triple
T29895578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarlet Lady-class |
E759267
|
entity |
| Predicate | firstOperatorService |
P120239
|
FINISHED |
| Object | Virgin Voyages |
—
|
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: Virgin Voyages | Statement: [Scarlet Lady-class, firstOperatorService, Virgin Voyages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOperatorService Context triple: [Scarlet Lady-class, firstOperatorService, Virgin Voyages]
-
A.
initialOperator
chosen
Indicates that an entity serves as the first or primary operator initiating a process, action, or operation involving another entity.
-
B.
typicalOperatorService
Indicates that an entity commonly performs or provides a particular operational service in a standard or expected manner.
-
C.
primaryOperator
Indicates that an entity serves as the main or leading operator responsible for performing or overseeing a specified operation or process in relation to another entity.
-
D.
openedFirstService
Indicates that one entity initiated or conducted the first instance of a particular service for another entity or in a given context.
-
E.
operatesService
Indicates that an agent runs, manages, or provides a particular service.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a0154b16a3c8190b808a460ae3a91ac |
completed | May 11, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_6a01539f19d88190b2de63f5262b1074 |
completed | May 11, 2026, 3:57 a.m. |
Created at: April 29, 2026, 6:04 p.m.