Triple
T27702638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian Zone |
E698465
|
entity |
| Predicate | hasTopSeeds |
P6982
|
FINISHED |
| Object | highest-ranked AFC national teams |
—
|
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: highest-ranked AFC national teams | Statement: [Asian Zone, hasTopSeeds, highest-ranked AFC national teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopSeeds Context triple: [Asian Zone, hasTopSeeds, highest-ranked AFC national teams]
-
A.
hasSeed
Indicates that one entity contains, produces, or is characterized by the presence of a seed associated with another entity.
-
B.
hasSeedCount
Indicates that an entity possesses a specific number of seeds.
-
C.
hasTopness
Indicates that an entity possesses the quantum property of topness, typically associated with the presence or contribution of a top quark.
-
D.
hasSeeding
chosen
Indicates that an entity is assigned or associated with a specific seeding position or rank, typically for ordering or placement in a competitive or structured context.
-
E.
topHas
Indicates that one entity possesses, contains, or is associated with another entity at the highest or most general level in a hierarchy or structure.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 2:58 p.m.