Triple
T27602649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saudi football league system |
E700091
|
entity |
| Predicate | hasClubLicensingRequirements |
P141668
|
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, hasClubLicensingRequirements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClubLicensingRequirements Context triple: [Saudi football league system, hasClubLicensingRequirements, true]
-
A.
hasLicensing
Indicates that one entity holds or is granted licensing rights, permissions, or authorization in relation to another entity or resource.
-
B.
hasLicenseCriteria
chosen
Indicates that an entity is subject to, or must satisfy, specific licensing requirements or conditions.
-
C.
requiresLicenseOf
Indicates that one entity must obtain or hold the license associated with another entity in order to use, access, or perform something.
-
D.
appliesToClub
Indicates that something (such as a rule, policy, attribute, or action) is relevant or applicable specifically to a particular club.
-
E.
hasClub
Indicates that an entity is associated with or belongs to a particular club.
- 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_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 2:08 p.m.