Triple
T30711616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haneullim |
E781908
|
entity |
| Predicate | partiallyComparableTo |
P25442
|
FINISHED |
| Object | Shangdi |
—
|
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: Shangdi | Statement: [Haneullim, partiallyComparableTo, Shangdi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyComparableTo Context triple: [Haneullim, partiallyComparableTo, Shangdi]
-
A.
partiallyCorrespondsTo
chosen
Indicates that one entity matches or aligns with another entity only in some aspects, segments, or components, rather than fully or exactly.
-
B.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
-
C.
sometimesComparedTo
Indicates that one entity is occasionally likened or contrasted to another, but not consistently or universally.
-
D.
isComparedTo
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
E.
hasComparableRank
Indicates that two entities hold positions or levels that are equivalent or similar in rank within a given hierarchy or system.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 29, 2026, 8:35 p.m.