Triple
T24754003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scotland national under-16 football team |
E619228
|
entity |
| Predicate | homeCountrySystem |
P147784
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [Scotland national under-16 football team, homeCountrySystem, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCountrySystem Context triple: [Scotland national under-16 football team, homeCountrySystem, United Kingdom]
-
A.
homeCountryDomesticSystem
chosen
Indicates that something is part of, governed by, or operating within the domestic system of its home country.
-
B.
homeCountryRegion
Indicates the country or broader geographic region that is considered the primary home or origin of an entity.
-
C.
governingSystemCountry
Indicates that a particular system of governance is the ruling or official governing system used by a given country.
-
D.
nativeCountry
Indicates the country in which an entity (typically a person) was born or is originally from.
-
E.
homeCountryProgram
Indicates that a program is associated with, based in, or primarily intended for participants from a particular home country.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:25 a.m.