Triple
T12739790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altınordu F.K. |
E304458
|
entity |
| Predicate | playerRecruitmentStrategy |
P100977
|
FINISHED |
| Object | focus on local talent |
—
|
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: focus on local talent | Statement: [Altınordu F.K., playerRecruitmentStrategy, focus on local talent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerRecruitmentStrategy Context triple: [Altınordu F.K., playerRecruitmentStrategy, focus on local talent]
-
A.
recommendedPlayers
Indicates the suggested or optimal number of players that should participate in an activity or game.
-
B.
recruitsFor
Indicates that one entity actively seeks out, enlists, or brings in participants, members, or resources on behalf of another entity, such as an organization, event, or cause.
-
C.
recruitedAs
Indicates that one entity has been brought into a role, position, or organization by another through a recruitment process.
-
D.
teamSelection
Indicates the assignment or choice of one or more individuals or entities to be part of a specific team.
-
E.
recruitingFocus
chosen
Indicates that an entity’s recruitment efforts are specifically directed toward or concentrated on another entity or group.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.