Triple
T5585284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EFL Championship under-21 team |
E146739
|
entity |
| Predicate | playerRegistration |
P3328
|
FINISHED |
| Object | registered with parent club |
—
|
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: registered with parent club | Statement: [EFL Championship under-21 team, playerRegistration, registered with parent club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerRegistration Context triple: [EFL Championship under-21 team, playerRegistration, registered with parent club]
-
A.
register
chosen
Indicates that an entity formally records or enrolls another entity or itself in an official system, list, or record.
-
B.
registrationSystem
Indicates a system or process responsible for recording, managing, and maintaining registrations or enrollments for entities.
-
C.
registrationCategory
Indicates the classification or type under which an entity is formally registered within a system or registry.
-
D.
supportsRegistration
Indicates that an entity provides the capability or functionality to handle or accept registration actions or processes.
-
E.
inscriptionBy
Indicates that an inscription was created, written, or carved by a particular agent or entity.
- 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.