Triple
T33442087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Anyang |
E856389
|
entity |
| Predicate | foundedAfterRelocationOf |
P1102
|
FINISHED |
| Object | Anyang LG Cheetahs to Seoul |
—
|
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: Anyang LG Cheetahs to Seoul | Statement: [FC Anyang, foundedAfterRelocationOf, Anyang LG Cheetahs to Seoul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAfterRelocationOf Context triple: [FC Anyang, foundedAfterRelocationOf, Anyang LG Cheetahs to Seoul]
-
A.
foundedByRelocation
Indicates that an entity came into existence or was established as a result of being relocated from another place or context.
-
B.
foundedAfterArrivalOf
Indicates that one entity was founded only after the arrival or appearance of another specified entity.
-
C.
laterRefoundedAs
Indicates that an entity was dissolved or ceased to exist and was subsequently re-established under a new or modified form, identity, or organization.
-
D.
foundedAfter
chosen
Indicates that one entity was founded at a later time than another entity.
-
E.
foundedBefore
Indicates that one entity was established or created at an earlier time than the other entity.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: May 1, 2026, 1:37 a.m.