Triple
T3018779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NISA |
E82402
|
entity |
| Predicate | competitionLevelRelativeToUSLChampionship |
P43092
|
FINISHED |
| Object | below USL Championship |
—
|
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: below USL Championship | Statement: [NISA, competitionLevelRelativeToUSLChampionship, below USL Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionLevelRelativeToUSLChampionship Context triple: [NISA, competitionLevelRelativeToUSLChampionship, below USL Championship]
-
A.
championshipLevel
Indicates the competitive tier or division in which a championship or title contest is held.
-
B.
joinedUSLChampionship
Indicates that an entity became a member or participant in the USL Championship league.
-
C.
competitionHierarchyLevel
chosen
Indicates the relative rank or tier of a competition within an overall competitive structure or hierarchy.
-
D.
competitionLevel
Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
-
E.
levelOfCompetition
Indicates the intensity or degree of competitive pressure present in a given context or interaction.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a927b608190ba1392498507b237 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961a97188190809dc73430a8eda8 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.