Triple
T25019564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pancake Rocks at Punakaiki |
E626533
|
entity |
| Predicate | surroundedByVegetation |
P953
|
FINISHED |
| Object | coastal rainforest |
—
|
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: coastal rainforest | Statement: [Pancake Rocks at Punakaiki, surroundedByVegetation, coastal rainforest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surroundedByVegetation Context triple: [Pancake Rocks at Punakaiki, surroundedByVegetation, coastal rainforest]
-
A.
vegetation
Indicates that an area or object is covered with, contains, or is characterized by plant life.
-
B.
locatedInForest
Indicates that an entity is situated within the boundaries of a forest.
-
C.
vegetationType
chosen
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
D.
hasVegetationRole
Indicates that an entity participates in or is assigned a specific functional role related to vegetation (such as growth, maintenance, or impact on plant life).
-
E.
hasNearbyWoodland
Indicates that one entity is located close to or in the immediate vicinity of a woodland area associated with another entity.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44ba9108c8190aca5c07f277d82b8 |
completed | May 1, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:06 a.m.