Triple
T22313654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Santa Cruz Island |
E551586
|
entity |
| Predicate | sandColorCause |
P23298
|
FINISHED |
| Object | crushed red organ-pipe coral fragments |
—
|
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: crushed red organ-pipe coral fragments | Statement: [Great Santa Cruz Island, sandColorCause, crushed red organ-pipe coral fragments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sandColorCause Context triple: [Great Santa Cruz Island, sandColorCause, crushed red organ-pipe coral fragments]
-
A.
hasSandColor
Indicates that one entity possesses or exhibits the sand-like color of another entity or color value.
-
B.
colorationCause
chosen
Indicates that one entity is the cause or source of the coloration observed in another entity.
-
C.
stoneColor
Indicates that one entity has a particular color attribute associated with a stone.
-
D.
colorOfSediment
Indicates the specific color or coloration characteristic associated with a given sediment.
-
E.
shadeColor
Indicates that one entity has a specific shade or variation of color associated with it.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15750f76c81909d6f788928f503f1 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.