Triple
T7357693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Residence (on selected A380 aircraft) |
E169666
|
entity |
| Predicate | serviceIncludes |
P14898
|
FINISHED |
| Object | dedicated butler |
—
|
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: dedicated butler | Statement: [The Residence (on selected A380 aircraft), serviceIncludes, dedicated butler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceIncludes Context triple: [The Residence (on selected A380 aircraft), serviceIncludes, dedicated butler]
-
A.
serviceComponentsInclude
chosen
Indicates that a service is composed of, or functionally includes, specific component elements.
-
B.
productIncludes
Indicates that a product contains, comprises, or is composed of the specified component, item, or feature.
-
C.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
D.
softwareIncluded
Indicates that certain software is bundled with, provided alongside, or contained within another item or offering.
-
E.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
- 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:06 p.m.