Triple
T222579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USL First Division |
E4247
|
entity |
| Predicate | fifaRecognized |
P8325
|
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: [USL First Division, fifaRecognized, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fifaRecognized Context triple: [USL First Division, fifaRecognized, true]
-
A.
FIFAcode
Indicates the standardized three-letter country or territory code assigned by FIFA to represent a national football team in international competitions.
-
B.
fifaLikeRankingType
Indicates a ranking system or classification that follows the style, rules, or methodology of FIFA’s official rankings.
-
C.
hasUEFACategory
Indicates that an entity is classified under a specific UEFA-defined category or tier.
-
D.
hasEsport
Indicates that an entity is associated with or participates in a specific electronic sports (esports) activity or competition.
-
E.
recognizedFor
Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with another entity.
- F. None of above. chosen
Provenance (4 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c705fd88190bfee7f5e1f7cee17 |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5617788190814358aee3f7ae37 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25c2bda788190bcfc0bc94686f9e0 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.