Triple
T22354959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | England national under-21 football team |
E552626
|
entity |
| Predicate | playerPoolSource |
P13374
|
FINISHED |
| Object | professional clubs in England |
—
|
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: professional clubs in England | Statement: [England national under-21 football team, playerPoolSource, professional clubs in England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerPoolSource Context triple: [England national under-21 football team, playerPoolSource, professional clubs in England]
-
A.
primaryPlayerSource
chosen
Indicates that an entity serves as the main origin or provider of a player within a given context or system.
-
B.
pools
Indicates that one entity combines resources, funds, or elements together with others into a shared collection or common pool.
-
C.
numberPool
Indicates that an entity is associated with or belongs to a specific pool or collection of numbers.
-
D.
samplingSource
Indicates that one entity serves as the origin or provider from which another entity is sampled or drawn.
-
E.
hasPlayerSource
Indicates that something originates from, is provided by, or is derived from a particular player.
- 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157ceb2308190941f6507e605a612 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.