Triple
T470236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USL Premier Development League |
E8538
|
entity |
| Predicate | playerStatus |
P13375
|
FINISHED |
| Object | unpaid amateur players |
—
|
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: unpaid amateur players | Statement: [USL Premier Development League, playerStatus, unpaid amateur players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerStatus Context triple: [USL Premier Development League, playerStatus, unpaid amateur players]
-
A.
teamState
Indicates the current status or condition of a team within a given context or process.
-
B.
statusInLeague
Indicates the standing or rank an entity holds within a particular league or competitive organization.
-
C.
exportStatus
Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
-
D.
playingPosition
Indicates the specific role or position an individual occupies while participating in a game or sport.
-
E.
sportsCountStatus
Indicates the status or condition of how many sports-related items or activities are present or counted.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efef8b788190857ebf66df562d59 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edecefb081908331ef8b9edf6636 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeba8a488190986cc7381332f783 |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.