Triple
T28532192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Mountain State Park |
E722072
|
entity |
| Predicate | rockWallLength |
P164615
|
FINISHED |
| Object | approximately 855 feet |
—
|
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: approximately 855 feet | Statement: [Fort Mountain State Park, rockWallLength, approximately 855 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rockWallLength Context triple: [Fort Mountain State Park, rockWallLength, approximately 855 feet]
-
A.
cityWallLength
Indicates the measured length or extent of a city's defensive wall.
-
B.
rockHeight
Indicates that a rock has a specified vertical measurement or elevation (its height).
-
C.
wallSlope
Indicates the angle or steepness of a wall surface relative to a reference plane (typically horizontal or vertical).
-
D.
hasWall
Indicates that one entity possesses, includes, or is bounded by a wall.
-
E.
enclosureWallHeight
Indicates the height of the wall that forms the boundary or enclosure around an area or structure.
- 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_69f64fd617588190904f94042d6f3eb1 |
completed | May 2, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 28, 2026, 3:29 a.m.