Triple
T32684356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomori Beach |
E835675
|
entity |
| Predicate | hasNaturalComposition |
P98201
|
FINISHED |
| Object | coral sand |
—
|
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: coral sand | Statement: [Tomori Beach, hasNaturalComposition, coral sand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNaturalComposition Context triple: [Tomori Beach, hasNaturalComposition, coral sand]
-
A.
hasNaturalForm
Indicates that an entity possesses an inherent, unaltered, or naturally occurring form or state.
-
B.
containsNaturallyOccurringElements
chosen
Indicates that something includes elements that occur in nature without human alteration or synthesis.
-
C.
hasNaturalCondition
Indicates that an entity possesses or is subject to a particular natural state, feature, or condition inherent to its environment or biology.
-
D.
hasNature
Indicates that something possesses, exhibits, or is characterized by a particular inherent quality, essence, or fundamental type.
-
E.
naturalOrArtificial
Indicates that something is classified as either naturally occurring or artificially created.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 1, 2026, 1:09 a.m.