Triple
T33207377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarsy |
E850049
|
entity |
| Predicate | hasRegionalParkStatus |
P204269
|
FINISHED |
| Object | within a regional natural park |
—
|
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: within a regional natural park | Statement: [Jarsy, hasRegionalParkStatus, within a regional natural park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalParkStatus Context triple: [Jarsy, hasRegionalParkStatus, within a regional natural park]
-
A.
hasRegionalPark
Indicates that a place or administrative area contains or is served by a designated regional park.
-
B.
hasRegionalParkSystem
Indicates that an entity possesses, manages, or is served by an organized system of regional parks.
-
C.
hasStateParkWithin
Indicates that one geographic or administrative area contains at least one state park located within its boundaries.
-
D.
hasProvinceParkSystem
Indicates that a province maintains and administers an official system of provincial parks.
-
E.
locatedInNationalParkOrQuasiNationalPark
Indicates that something is situated within the boundaries of a national park or a quasi-national park.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a035b78140081908e451cb63d3c1c7c |
completed | May 12, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_6a035af3d8f48190bf1f3741d374404e |
completed | May 12, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_6a035b773898819099125a5efc239d3e |
completed | May 12, 2026, 4:55 p.m. |
Created at: May 1, 2026, 1:30 a.m.