Triple
T9294141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongsan Garrison |
E223596
|
entity |
| Predicate | plannedReuse |
P12134
|
FINISHED |
| Object | public 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: public park | Statement: [Yongsan Garrison, plannedReuse, public park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedReuse Context triple: [Yongsan Garrison, plannedReuse, public park]
-
A.
plannedUseOf
chosen
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
-
B.
planned
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
-
C.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
D.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
E.
plannedVia
Indicates that something is arranged, organized, or scheduled by means of a particular method, process, or intermediary.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd089a2ed0819086b2e4219ff2453e |
completed | April 1, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.