Triple
T27602648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saudi football league system |
E700091
|
entity |
| Predicate | hasForeignPlayerRegulations |
P149473
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Saudi football league system, hasForeignPlayerRegulations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasForeignPlayerRegulations Context triple: [Saudi football league system, hasForeignPlayerRegulations, true]
-
A.
allowsForeignPlayers
Indicates that an entity permits participation or involvement by players who are from foreign countries or outside its primary jurisdiction.
-
B.
foreignPlayerRosterLimit
Indicates a restriction on how many foreign or non-local players may be included on a team’s roster.
-
C.
fifaEligibilityRule
Indicates that a person meets the official criteria set by FIFA to represent a particular national team in international football competitions.
-
D.
usesDomesticPlayers
Indicates that an entity relies on or fields players who are from its own country or domestic system.
-
E.
leagueRestriction
chosen
Indicates a constraint or rule that limits participation, eligibility, or activity within a particular league.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 2:08 p.m.