Triple
T7828324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korea Football Association |
E181300
|
entity |
| Predicate | AFCMemberSince |
P76942
|
FINISHED |
| Object | 1954 |
—
|
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: 1954 | Statement: [Korea Football Association, AFCMemberSince, 1954]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AFCMemberSince Context triple: [Korea Football Association, AFCMemberSince, 1954]
-
A.
AFLMembershipStartYear
Indicates the year in which an entity first became a member of the AFL.
-
B.
joinedAFC
chosen
Indicates that an entity became a member of or affiliated with the AFC (Asian Football Confederation) at a particular point in time.
-
C.
AFLMembershipEndYear
Indicates the year in which an entity’s membership in the AFL (Australian Football League) ends or is scheduled to end.
-
D.
fifaAffiliationDate
Indicates the date on which an entity formally became affiliated with FIFA.
-
E.
AFLFoundingMember
Indicates that an entity was among the original founding members involved in establishing the AFL (Australian Football League or its predecessor).
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb04a97d748190b1924890b1328bf1 |
completed | March 30, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:43 p.m.