Triple
T36363044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zip World Slate Caverns |
E895545
|
entity |
| Predicate | materialOfSurroundings |
P185414
|
FINISHED |
| Object | slate |
—
|
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: slate | Statement: [Zip World Slate Caverns, materialOfSurroundings, slate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialOfSurroundings Context triple: [Zip World Slate Caverns, materialOfSurroundings, slate]
-
A.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
B.
materialDepicted
Indicates that a work or representation visually portrays or includes a particular material as part of its subject.
-
C.
hasSurroundings
Indicates that an entity is located within or encircled by a particular environment, context, or set of surrounding elements.
-
D.
surrounds
Indicates that one entity is located all around another entity, enclosing or encircling it on multiple sides or completely.
-
E.
surfaceTypeAround
Indicates the type or nature of the surface that surrounds or is immediately adjacent to a given 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.