Triple
T25304853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miryang Eupseong site |
E634452
|
entity |
| Predicate | isRemainsOf |
P35040
|
FINISHED |
| Object | Miryang Eupseong fortress town |
—
|
NE NERFINISHED |
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: Miryang Eupseong fortress town | Statement: [Miryang Eupseong site, isRemainsOf, Miryang Eupseong fortress town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRemainsOf Context triple: [Miryang Eupseong site, isRemainsOf, Miryang Eupseong fortress town]
-
A.
hasRemainsOf
Indicates that one entity physically contains, preserves, or is associated with the leftover physical traces or remnants of another entity.
-
B.
remainedIn
Indicates that an entity stayed within or continued to be located in a particular place or state for a period of time.
-
C.
hasRemainderTo
Indicates that one quantity leaves a specified remainder when divided by another quantity.
-
D.
visibleRemains
chosen
Indicates that some physical remnants of an entity or event can still be seen or visually detected.
-
E.
estimatedNumberOfRemains
Indicates the approximate count of human or other remains associated with an entity, based on estimation rather than an exact measurement.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f49399bf3881908b36a2b009be4f87 |
completed | May 1, 2026, 11:50 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:25 p.m.