Triple
T18557023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherry Springs State Park |
E453529
|
entity |
| Predicate | managesLightUse |
P132146
|
FINISHED |
| Object | red-light-only rules on astronomy field |
—
|
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: red-light-only rules on astronomy field | Statement: [Cherry Springs State Park, managesLightUse, red-light-only rules on astronomy field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesLightUse Context triple: [Cherry Springs State Park, managesLightUse, red-light-only rules on astronomy field]
-
A.
lightingControlledBy
Indicates that the lighting system or device is operated, regulated, or influenced by a specified controller or control mechanism.
-
B.
canLight
Indicates that one entity has the ability or capacity to provide or emit light to another entity or environment.
-
C.
lightOrganFunction
Indicates that one entity serves as the functional light-producing organ or structure for another entity.
-
D.
lightPeriod
Indicates the duration or interval during which light is present or active in a given context.
-
E.
lightRange
Indicates the distance or area over which a light source effectively emits or illuminates.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53806d2a08190963f4d8e927a247f |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:39 a.m.