Triple
T24662050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chondoism |
E610563
|
entity |
| Predicate | hasSuccessorLeader |
P157668
|
FINISHED |
| Object | Son Byeong-hui |
—
|
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: Son Byeong-hui | Statement: [Chondoism, hasSuccessorLeader, Son Byeong-hui]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessorLeader Context triple: [Chondoism, hasSuccessorLeader, Son Byeong-hui]
-
A.
hasSiblingLeaders
Indicates that the entities are leaders who are siblings of each other.
-
B.
hasOnlineSuccessor
Indicates that one entity is the direct online or digital successor of another, typically replacing or continuing its function in an online context.
-
C.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
D.
hasSuccessorUsers
Indicates that one user or set of users is followed or replaced by another user or set of users in a sequence or succession.
-
E.
hasFlagshipSuccessor
Indicates that one entity serves as the primary or leading successor to another, typically replacing it as the main or flagship version, product, or instance.
- F. None of above. chosen
Provenance (4 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 2:34 a.m.