Triple
T29106545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lee Sedol |
E736776
|
entity |
| Predicate | goAffiliation |
P74283
|
FINISHED |
| Object | Korea Baduk Association |
—
|
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: Korea Baduk Association | Statement: [Lee Sedol, goAffiliation, Korea Baduk Association]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goAffiliation Context triple: [Lee Sedol, goAffiliation, Korea Baduk Association]
-
A.
affiliationStart
Indicates the point in time when an entity’s formal association or membership with another entity begins.
-
B.
groupAffiliation
chosen
Indicates that an entity is associated with, belongs to, or is a member of a particular group or organization.
-
C.
allowsAffiliationOf
Indicates that one entity grants permission or enables another entity to establish or hold an affiliation with it.
-
D.
affiliationSystem
Indicates a formal connection between an entity and an organizational, institutional, or structural system with which it is associated or aligned.
-
E.
builderAffiliation
Indicates the organizational, institutional, or group association that a builder is connected to or works under.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661ba062881909fa3d7b23938e2ab |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:16 a.m.