Triple
T5088451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 61 (Rust and Blue) |
E114693
|
entity |
| Predicate | edgeTreatment |
P60645
|
FINISHED |
| Object | soft edges |
—
|
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: soft edges | Statement: [No. 61 (Rust and Blue), edgeTreatment, soft edges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: edgeTreatment Context triple: [No. 61 (Rust and Blue), edgeTreatment, soft edges]
-
A.
formsEdgeOf
Indicates that one entity constitutes a boundary or outer limit of another entity.
-
B.
sharesBorderType
Indicates that two entities are connected by a common boundary characterized by the same specified type of border (e.g., land, river, maritime).
-
C.
ribbonEdgeColor
Indicates the color assigned to the edge or border of a ribbon in a visualization or graphical representation.
-
D.
typicalEdge
Indicates a standard or representative connection between two entities, as opposed to a special or exceptional type of edge.
-
E.
borderColor
Indicates the color that forms the boundary or outline of an 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75219a94819094fc54c1df448470 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd715c0a448190afc837c6c31dc6ab |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd72b8d7a88190ad53fae64f17e22c |
completed | March 20, 2026, 4:15 p.m. |
Created at: March 20, 2026, 1:40 p.m.