Triple
T1977026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Composition with Red, Blue and Yellow |
E42937
|
entity |
| Predicate | hasOrientationOfLines |
P4984
|
FINISHED |
| Object | vertical |
—
|
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: vertical | Statement: [Composition with Red, Blue and Yellow, hasOrientationOfLines, vertical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrientationOfLines Context triple: [Composition with Red, Blue and Yellow, hasOrientationOfLines, vertical]
-
A.
hasOrientation
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
B.
hasStraightLines
Indicates that the related entity possesses or is characterized by straight, non-curved lines.
-
C.
hasStripeOrientation
chosen
Indicates the directional arrangement or alignment of stripes present on an entity.
-
D.
isLinedWith
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
-
E.
hasFieldOrientation
Indicates that one entity has a specified directional or spatial orientation relative to a field (such as magnetic, electric, or visual field).
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f9a87c8190816db3888787ad76 |
completed | March 7, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69abaff9a09c8190a81fa13f4b85bc79 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.