Triple
T25520049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mushroom Rock State Park |
E639620
|
entity |
| Predicate | hasNotableRock |
P138728
|
FINISHED |
| Object | large mushroom-shaped pedestal rock |
—
|
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: large mushroom-shaped pedestal rock | Statement: [Mushroom Rock State Park, hasNotableRock, large mushroom-shaped pedestal rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableRock Context triple: [Mushroom Rock State Park, hasNotableRock, large mushroom-shaped pedestal rock]
-
A.
hasNotableBoulder
chosen
Indicates that an entity possesses or features a boulder that is considered notable or significant in some way.
-
B.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
C.
hasRockGrade
Indicates that an entity is associated with a specific difficulty or quality grade used to classify rock climbing routes or rock features.
-
D.
hasRockRecord
Indicates that an entity possesses or is associated with a documented record related to rock music or rock materials.
-
E.
hasNearbyRockFormation
Indicates that one entity is located close to or adjacent to a rock formation.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 21, 2026, 2:59 p.m.