Triple
T37989957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasas SC |
E947796
|
entity |
| Predicate | hasYouthAcademyInSport |
P163757
|
FINISHED |
| Object | football |
—
|
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: football | Statement: [Vasas SC, hasYouthAcademyInSport, football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYouthAcademyInSport Context triple: [Vasas SC, hasYouthAcademyInSport, football]
-
A.
hasYouthTeam
Indicates that an entity has an associated youth team that serves as its junior or developmental squad.
-
B.
usesYouthAcademyPipeline
chosen
Indicates that an organization develops and promotes players through its own youth academy system as a primary source of talent.
-
C.
hasYouthProgram
Indicates that an entity offers or is associated with an organized program or set of activities specifically designed for young people.
-
D.
youthSport
Indicates a relationship where an individual participates in or is associated with a sport specifically organized for young people.
-
E.
includesYouthLeagues
Indicates that the subject entity offers, contains, or is associated with organized leagues or programs specifically for youth participants.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.