Triple
T30754034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoshinogari Historical Park |
E783030
|
entity |
| Predicate | publicParkOpened |
P44881
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Yoshinogari Historical Park, publicParkOpened, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicParkOpened Context triple: [Yoshinogari Historical Park, publicParkOpened, 1992]
-
A.
openedInPark
Indicates that an entity was opened, inaugurated, or began operating within the boundaries of a park.
-
B.
cityParkStatus
Indicates the current operational or accessibility status of a city park in relation to its governing jurisdiction or management.
-
C.
openedWithPark
Indicates that something (such as an event, show, or sequence) began or was initiated with a segment, performance, or feature involving a park.
-
D.
parkSectionOpening
Indicates that a specific section of a park is opening or becoming available for use, typically at a particular time or under certain conditions.
-
E.
openingDateAsPark
chosen
Indicates the date on which a place or area was first officially opened and began operating as a park.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: April 29, 2026, 8:39 p.m.