Triple
T33647748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DREAMJET |
E862006
|
entity |
| Predicate | specializesInOperatorService |
P5884
|
FINISHED |
| Object | all-business-class transatlantic service |
—
|
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: all-business-class transatlantic service | Statement: [DREAMJET, specializesInOperatorService, all-business-class transatlantic service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specializesInOperatorService Context triple: [DREAMJET, specializesInOperatorService, all-business-class transatlantic service]
-
A.
typicalOperatorService
Indicates that an entity commonly performs or provides a particular operational service in a standard or expected manner.
-
B.
operatesService
chosen
Indicates that an agent runs, manages, or provides a particular service.
-
C.
typicalOperator
Indicates that an entity commonly or normally performs operations on, or acts upon, another entity in a standard or expected manner.
-
D.
otherOperator
Indicates a relationship where one operator is distinguished from, or serves as an alternative to, another operator within the same context or system.
-
E.
operatesServiceTo
Indicates that one entity runs or provides a transportation or service route to another entity or location.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 1:42 a.m.