Triple
T27209243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tintin in the Congo |
E683953
|
entity |
| Predicate | hasColorizedVersion |
P198233
|
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: [Tintin in the Congo, hasColorizedVersion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColorizedVersion Context triple: [Tintin in the Congo, hasColorizedVersion, yes]
-
A.
hasColorDisplay
Indicates that an entity is equipped with a display capable of showing colors rather than only monochrome output.
-
B.
hasColorInfo
Indicates that an entity is associated with specific color-related information or attributes.
-
C.
hasColorTraces
Indicates that an entity shows small or partial amounts of a particular color, rather than being fully that color.
-
D.
hasColorProcess
Indicates a relationship where an entity is associated with a specific method or process used to apply, change, or manage its color.
-
E.
hasColorSymbol
Indicates that one entity is associated with another entity that serves as its representative or symbolic color.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
| PDg | Predicate description generation | batch_69fed48c92ec8190b3be88880d86de86 |
completed | May 9, 2026, 6:30 a.m. |
Created at: April 27, 2026, 9:39 a.m.