Triple
T12549011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseon Chongdokbu Cheongsa |
E300046
|
entity |
| Predicate | standsOnFormerly |
P55436
|
FINISHED |
| Object | royal palace site |
—
|
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: royal palace site | Statement: [Joseon Chongdokbu Cheongsa, standsOnFormerly, royal palace site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standsOnFormerly Context triple: [Joseon Chongdokbu Cheongsa, standsOnFormerly, royal palace site]
-
A.
formerlyLocatedOn
chosen
Indicates that an entity was once located on or situated upon another entity, but is no longer in that position.
-
B.
hasStandsOn
Indicates that one entity is physically supported by and in contact with the upper surface of another entity.
-
C.
hasStand
Indicates that an entity possesses, is equipped with, or is supported by a stand or base structure.
-
D.
isStandOf
Indicates that one entity serves as the Stand (a supernatural or personified power) belonging to or associated with another entity.
-
E.
formerlyListedOn
Indicates that an entity was previously listed on a particular exchange, registry, or listing platform but is no longer listed there.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:58 p.m.