Triple
T38079226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jangchok Cheonwang |
E950805
|
entity |
| Predicate | guardOfDirection |
P101901
|
FINISHED |
| Object | south |
—
|
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: south | Statement: [Jangchok Cheonwang, guardOfDirection, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardOfDirection Context triple: [Jangchok Cheonwang, guardOfDirection, south]
-
A.
directionGuarded
chosen
Indicates that one entity protects, blocks, or oversees another entity specifically from a given direction or along a particular directional axis.
-
B.
guard
Indicates that one entity protects, watches over, or defends another entity or resource from harm, intrusion, or unauthorized access.
-
C.
guardFeature
Indicates that one entity protects, secures, or restricts access to a particular feature of another entity.
-
D.
guardType
Indicates the specific kind or category of guarding role or protection associated with an entity.
-
E.
guardian
Indicates a protective or custodial relationship in which one entity is responsible for the care, safety, or oversight of another.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:21 p.m.