Triple
T2926288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brocken spectre |
E78851
|
entity |
| Predicate | hasColorPattern |
P22465
|
FINISHED |
| Object | glory shows concentric colored rings |
—
|
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: glory shows concentric colored rings | Statement: [Brocken spectre, hasColorPattern, glory shows concentric colored rings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColorPattern Context triple: [Brocken spectre, hasColorPattern, glory shows concentric colored rings]
-
A.
hasColorSymbol
Indicates that one entity is associated with another entity that serves as its representative or symbolic color.
-
B.
hasColorOption
Indicates that an entity offers or supports a particular color as one of its selectable options.
-
C.
hasColorProcess
Indicates a relationship where an entity is associated with a specific method or process used to apply, change, or manage its color.
-
D.
hasColoration
chosen
Indicates that an entity possesses a particular color or pattern of colors.
-
E.
hasColorSegments
Indicates that an entity is composed of or divided into distinct parts, each associated with a specific color.
- 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:55 p.m.