Triple
T27000261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney Wonder |
E680082
|
entity |
| Predicate | exteriorColorScheme |
P19770
|
FINISHED |
| Object | black hull with red funnels and yellow lifeboats |
—
|
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: black hull with red funnels and yellow lifeboats | Statement: [Disney Wonder, exteriorColorScheme, black hull with red funnels and yellow lifeboats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exteriorColorScheme Context triple: [Disney Wonder, exteriorColorScheme, black hull with red funnels and yellow lifeboats]
-
A.
exteriorColor
chosen
Indicates the relationship that specifies the color on the outside surface of an entity.
-
B.
façadeColorScheme
Indicates the relationship specifying the color arrangement or palette applied to the exterior façade of a structure.
-
C.
trunkColorDesignation
Indicates the specified color assigned to the trunk of an object (such as a tree or similar structure).
-
D.
hasInteriorColor
Indicates that an entity possesses a specific color used on its interior surfaces or internal parts.
-
E.
hasRoofColor
Indicates that an entity possesses a roof whose color is the specified value.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621cbc48881908d104c648c91c715 |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:57 a.m.