Triple
T37566981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springbok Sevens |
E933981
|
entity |
| Predicate | fifaCountryCodeStyle |
P6278
|
FINISHED |
| Object | RSA |
—
|
NE NERFINISHED |
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: RSA | Statement: [Springbok Sevens, fifaCountryCodeStyle, RSA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fifaCountryCodeStyle Context triple: [Springbok Sevens, fifaCountryCodeStyle, RSA]
-
A.
fifaCodeUsedBy
Indicates that a specific FIFA country or team code is used to represent or identify a particular team, association, or entity in the context of FIFA competitions or records.
-
B.
fifaAffiliationCountry
Indicates that a country is affiliated with or recognized by FIFA as a member football association.
-
C.
fifaCodePreviously
Indicates that an entity previously had a specific FIFA code before it was changed or replaced.
-
D.
fifaCodeStatus
Indicates the status or condition of an entity’s FIFA-assigned code, such as whether it is active, valid, or otherwise classified.
-
E.
FIFAcode
chosen
Indicates the standardized three-letter country or territory code assigned by FIFA to represent a national football team in international competitions.
- 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba61dff5081909fec88a7aeb0c8a1 |
completed | May 6, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69fba350e9a8819095893229d9643572 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.