Triple
T2462011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schindler's List |
E54552
|
entity |
| Predicate | containsColorSequences |
P40659
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Schindler's List, containsColorSequences, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsColorSequences Context triple: [Schindler's List, containsColorSequences, yes]
-
A.
hasColorSegments
Indicates that an entity is composed of or divided into distinct parts, each associated with a specific color.
-
B.
hasColorProcess
Indicates a relationship where an entity is associated with a specific method or process used to apply, change, or manage its color.
-
C.
hasColorSymbol
Indicates that one entity is associated with another entity that serves as its representative or symbolic color.
-
D.
hasColorPlay
Indicates a relationship where something exhibits or incorporates playful or varied use of color.
-
E.
hasColorReference
Indicates that one entity serves as a reference or source for determining or specifying the color associated with another entity.
- F. None of above. chosen
Provenance (4 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_69ab49dee84c819096b50a0049c347ac |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd49c5aa081909ab4f726a458b77f |
completed | March 7, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69abd0b199488190aa381b36593ae1ac |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd49b5d2481908817aeb171e2bd61 |
completed | March 7, 2026, 7:32 a.m. |
Created at: March 6, 2026, 9:44 p.m.