Triple
T28532196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Mountain State Park |
E722072
|
entity |
| Predicate | rockWallAttribution |
P166224
|
FINISHED |
| Object | Native American origin (hypothesized) |
—
|
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: Native American origin (hypothesized) | Statement: [Fort Mountain State Park, rockWallAttribution, Native American origin (hypothesized)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rockWallAttribution Context triple: [Fort Mountain State Park, rockWallAttribution, Native American origin (hypothesized)]
-
A.
rockWallLength
Indicates the measured linear extent or distance from one end of a rock wall to the other.
-
B.
rockWallPeriod
Indicates a time span during which a rock wall exists, is in use, or is relevant.
-
C.
wallSlope
Indicates the angle or steepness of a wall surface relative to a reference plane (typically horizontal or vertical).
-
D.
wallFeature
Indicates that one entity functions as a structural or design feature associated with a wall of another entity.
-
E.
hasWallText
Indicates that an entity features or is associated with text displayed on a wall, such as inscriptions, labels, or written information.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 3:29 a.m.