Triple
T21778378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Pike (Wasdale) |
E537640
|
entity |
| Predicate | hasColourOrigin |
P53192
|
FINISHED |
| Object | reddish rock |
—
|
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: reddish rock | Statement: [Red Pike (Wasdale), hasColourOrigin, reddish rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColourOrigin Context triple: [Red Pike (Wasdale), hasColourOrigin, reddish rock]
-
A.
colorOrigin
chosen
Indicates the source or cause from which an entity’s color is derived or determined.
-
B.
hasDesignOrigin
Indicates that one entity is the source, inspiration, or original model from which the design of another entity is derived.
-
C.
hasTraditionalColors
Indicates that an entity is associated with colors that are traditionally or customarily linked to it.
-
D.
originalColors
Indicates that something retains or is associated with its initial, unaltered set of colors.
-
E.
hasCapColor
Indicates that an entity possesses a cap whose color is specified by the related value.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0462b094c81908207073c278a58fe |
completed | April 28, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:51 p.m.