Triple
T18107089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFC Champions League |
E433371
|
entity |
| Predicate | confederationMemberCount |
P8912
|
FINISHED |
| Object | 47 |
—
|
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: 47 | Statement: [AFC Champions League, confederationMemberCount, 47]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confederationMemberCount Context triple: [AFC Champions League, confederationMemberCount, 47]
-
A.
associatedConfederationCount
chosen
Indicates the number of distinct confederations with which an entity is associated.
-
B.
numberOfMemberStates
Indicates the total count of member states associated with a given entity or organization.
-
C.
associatedConfederation
Indicates a relationship where an entity is linked to, belongs to, or is formally connected with a specific confederation.
-
D.
confederationsRepresented
Indicates that one entity serves as an official representative or member of one or more confederations within a given context.
-
E.
confederation1
Indicates a relationship where multiple entities join together in a loose alliance or union while retaining their individual autonomy.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddbb3d408190b5fc7870bc6512f4 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.