Triple
T10744346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPHL |
E253411
|
entity |
| Predicate | isTeamBasedLeague |
P51022
|
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: [SPHL, isTeamBasedLeague, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTeamBasedLeague Context triple: [SPHL, isTeamBasedLeague, true]
-
A.
isTeamCompetition
chosen
Indicates that the competition involves participants organized into teams competing against each other rather than as individuals.
-
B.
isPartOfLeague
Indicates that an entity belongs to, participates in, or is a member of a particular league.
-
C.
basedOnLeague
Indicates that one entity is determined, structured, or derived according to the rules, structure, or membership of a particular league.
-
D.
isTeamSpecific
Indicates that something applies only to, or is restricted to, a particular team rather than being general or shared across multiple teams.
-
E.
basedInLeague
Indicates that an entity (such as a team or club) participates in, belongs to, or is officially associated with 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d711b6b4b48190bad08500fa963062 |
completed | April 9, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.