Triple
T24285174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Youth Football competitions |
E605649
|
entity |
| Predicate | talentIdentificationMethod |
P750
|
FINISHED |
| Object | scouting at matches |
—
|
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: scouting at matches | Statement: [Russian Youth Football competitions, talentIdentificationMethod, scouting at matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: talentIdentificationMethod Context triple: [Russian Youth Football competitions, talentIdentificationMethod, scouting at matches]
-
A.
discoversTalentOf
Indicates that one entity identifies or recognizes the talent or abilities possessed by another entity.
-
B.
assessmentMethod
chosen
Indicates the method or procedure used to evaluate, measure, or judge something.
-
C.
skillAssessed
Indicates that an entity’s skill or competency has been evaluated or measured, typically by another agent or process.
-
D.
notableRecruitingSkill
Indicates that an entity is recognized for having significant or distinguished ability in recruiting others.
-
E.
indicatesSkill
Indicates a relationship where one entity possesses, demonstrates, or is associated with a particular skill represented by another 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5605f081908367bd08ab1ec9ab |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.