Triple
T37360463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clockwork Orange (football) |
E927562
|
entity |
| Predicate | associatedWithClubInfluence |
P156643
|
FINISHED |
| Object | AFC Ajax |
E298354
|
NE 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: AFC Ajax | Statement: [Clockwork Orange (football), associatedWithClubInfluence, AFC Ajax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithClubInfluence Context triple: [Clockwork Orange (football), associatedWithClubInfluence, AFC Ajax]
-
A.
influenceOnClub
chosen
Indicates that one entity has an effect on, shapes, or alters the state, performance, or direction of a club.
-
B.
relatedToClub
Indicates that there is an association or connection between an entity and a club, without specifying the exact nature of that relationship.
-
C.
associatedWithClubSuccess
Indicates that an entity has a meaningful connection or contribution to the success or achievements of a club.
-
D.
associatedClub2
Indicates that an entity has a secondary or additional affiliation or membership with a particular club.
-
E.
associatedClubOwner
Indicates that there is an ownership or proprietorship relationship between a club and its associated owner.
- F. None of above.
Provenance (4 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a406ce71e488190a4e0d40d4388f884 |
completed | June 28, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.