Triple
T5585276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EFL Championship under-21 team |
E146739
|
entity |
| Predicate | typicalStaffRole |
P18942
|
FINISHED |
| Object | under-21 head coach |
—
|
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: under-21 head coach | Statement: [EFL Championship under-21 team, typicalStaffRole, under-21 head coach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStaffRole Context triple: [EFL Championship under-21 team, typicalStaffRole, under-21 head coach]
-
A.
typicalRole
chosen
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
B.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
C.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
D.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
E.
roleInCommandStructure
Indicates that one entity holds a specific position or function within the hierarchical command structure of another entity or organization.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02085d0e48190b8d185fe7f3d8579 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.