Triple
T8494894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgin logo |
E201072
|
entity |
| Predicate | commonlyPlacedOn |
P33560
|
FINISHED |
| Object | aircraft liveries |
—
|
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: aircraft liveries | Statement: [Virgin logo, commonlyPlacedOn, aircraft liveries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyPlacedOn Context triple: [Virgin logo, commonlyPlacedOn, aircraft liveries]
-
A.
commonlyFoundOn
chosen
Indicates that one entity is typically or frequently located on, attached to, or present upon another entity.
-
B.
canBePlacedUnder
Indicates that one entity is allowed or able to be positioned beneath another entity in a spatial or structural arrangement.
-
C.
commonlyDepictedOn
Indicates that something is frequently shown or represented on the surface, medium, or context of another thing.
-
D.
typicalStorePlacement
Indicates the usual or standard physical location where an item is placed or displayed within a store.
-
E.
seatOftenLocatedIn
Indicates that one type of seat is commonly or typically found within a particular location or setting.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe57c01f881908cb77c8c834ac08d |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.