Triple
T759877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raith Rovers F.C. |
E16042
|
entity |
| Predicate | hasYouthSystem |
P6626
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Raith Rovers F.C., hasYouthSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYouthSystem Context triple: [Raith Rovers F.C., hasYouthSystem, yes]
-
A.
hasYouthProgram
chosen
Indicates that an entity offers or is associated with an organized program or set of activities specifically designed for young people.
-
B.
playedForJuniorTeam
Indicates that an individual was a member of and played for a specific junior-level sports team.
-
C.
youthWing
Indicates that one organization serves as the youth or junior wing of another organization, typically representing younger members aligned with the parent body.
-
D.
typeOfLeagueSystem
Indicates that one entity is the kind or structure of league system to which another entity belongs or in which it operates.
-
E.
hasCadetBranch
Indicates that one lineage, family, or house is a junior or offshoot branch derived from another main or senior line.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a68158508190998da10e69252662 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a5048a8081908d0542214142664a |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.