Triple
T18755737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pinnacles Coloured Sands |
E458643
|
entity |
| Predicate | isFragile |
P103540
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Pinnacles Coloured Sands, isFragile, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFragile Context triple: [The Pinnacles Coloured Sands, isFragile, true]
-
A.
fragility
chosen
Indicates that an entity is easily damaged, broken, or adversely affected when subjected to stress, force, or change.
-
B.
hasFragrance
Indicates that one entity possesses or emits a particular scent or aroma associated with another entity.
-
C.
isDuctile
Indicates that an entity can be drawn out or stretched into a thin wire or shape without breaking.
-
D.
shippingRisk
Indicates the level or likelihood of potential loss, damage, or delay associated with transporting goods from one location to another.
-
E.
hasFrill
Indicates that one entity possesses or is characterized by a frill as a distinguishing feature or component.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579f20b808190833e29830bfed937 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.