Triple
T37438734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertha BSC II |
E930350
|
entity |
| Predicate | usesPlayerCategory |
P78944
|
FINISHED |
| Object | youth players |
—
|
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: youth players | Statement: [Hertha BSC II, usesPlayerCategory, youth players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPlayerCategory Context triple: [Hertha BSC II, usesPlayerCategory, youth players]
-
A.
hasInGameCategory
Indicates that an in-game item, action, or entity belongs to a specific predefined category within the game’s classification system.
-
B.
playsCategory
Indicates that an entity engages in or performs activities belonging to a specified category.
-
C.
usesCategorySystem
chosen
Indicates that one entity organizes or classifies things according to a particular category system defined by another entity.
-
D.
controlsPlayerEligibility
Indicates a relationship where one entity determines or regulates whether a player is allowed to participate.
-
E.
supportsPlayer
Indicates that one entity provides assistance, resources, or backing to a player in achieving their goals or performing actions.
- 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 3, 2026, 4:17 p.m.