Triple
T6840710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birmingham Legion FC |
E157564
|
entity |
| Predicate | belongsToLeagueSystem |
P2687
|
FINISHED |
| Object | USL system |
—
|
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: USL system | Statement: [Birmingham Legion FC, belongsToLeagueSystem, USL system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToLeagueSystem Context triple: [Birmingham Legion FC, belongsToLeagueSystem, USL system]
-
A.
associatedLeagueCodeSystem
Indicates that there is a relationship linking an entity to the code system used by a particular league.
-
B.
representsInLeague
Indicates that an entity serves as a representative of another entity within a specific league or organized competition.
-
C.
isPartOfLeague
Indicates that an entity belongs to, participates in, or is a member of a particular league.
-
D.
includesLeague
chosen
Indicates that an entity (such as a competition, organization, or system) contains or encompasses a specific league as one of its components.
-
E.
eligibleLeague
Indicates that an entity (such as a team or player) is qualified or permitted to participate in 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6b4a1f88190b4f532828697fbd8 |
completed | March 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:19 p.m.