Triple
T6980600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crewe Alexandra F.C. |
E161832
|
entity |
| Predicate | academyFocus |
P6235
|
FINISHED |
| Object | technical development |
—
|
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: technical development | Statement: [Crewe Alexandra F.C., academyFocus, technical development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: academyFocus Context triple: [Crewe Alexandra F.C., academyFocus, technical development]
-
A.
academyClass
Indicates that an entity is a class, course, or instructional grouping offered within an academy or educational institution.
-
B.
educationalFocus
chosen
Indicates the primary subject area or theme that an educational activity, program, or resource is centered on.
-
C.
youthAcademyFocus
Indicates that an organization or program is primarily dedicated to developing and training young or junior participants.
-
D.
academicFocus
Indicates the primary field of study, discipline, or subject area that an entity concentrates on academically.
-
E.
developmentAcademy
Indicates a relationship where an academy is responsible for or involved in the development, training, or educational advancement of individuals or groups.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db6c1efc8190ab1575ae2ce726db |
completed | March 27, 2026, 7:33 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:31 p.m.