Triple
T22744169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Korea women's national basketball team |
E562501
|
entity |
| Predicate | homeContinentCode |
P32867
|
FINISHED |
| Object | AS |
—
|
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: AS | Statement: [South Korea women's national basketball team, homeContinentCode, AS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeContinentCode Context triple: [South Korea women's national basketball team, homeContinentCode, AS]
-
A.
homeCountryRegion
Indicates the country or broader geographic region that is considered the primary home or origin of an entity.
-
B.
homeContinentConfederation
Indicates the confederation that governs or represents the continent where an entity is based or originates.
-
C.
continentOfResidence
chosen
Indicates the continent on which a given entity currently resides or is based.
-
D.
countryOrRegion
Indicates that one entity is a country or geographic region associated with another entity (such as its location, jurisdiction, or area of relevance).
-
E.
continentOfUse
Indicates the continent where something is primarily used or in effect.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1797590f08190a784f73fcd27b101 |
completed | April 29, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:23 p.m.