Triple
T11834102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feyenoord |
E281470
|
entity |
| Predicate | rival |
P437
|
FINISHED |
| Object | Ajax |
E386269
|
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: Ajax | Statement: [Feyenoord, rival, Ajax]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ajax Context triple: [Feyenoord, rival, Ajax]
-
A.
Ajax
Ajax is a long-standing household cleaning product brand known for its powdered and liquid cleaners, owned by Colgate-Palmolive.
-
B.
Ajax
Ajax is a suburban town in the eastern part of the Greater Toronto Area in Ontario, Canada, known for its residential communities and growing commercial development along Lake Ontario.
-
C.
Ajax
Ajax is a modern British Army armoured fighting vehicle designed for advanced reconnaissance, surveillance, and battlefield intelligence roles.
-
D.
Ajax
Ajax is an ancient Greek tragedy by Sophocles that dramatizes the downfall and suicide of the great warrior Ajax after the Trojan War.
-
E.
Ajax
chosen
Ajax is a renowned Dutch football club from Amsterdam, famous for its successful history, attacking style of play, and prolific youth academy.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a62e7e408190998bebe346c82e89 |
completed | April 10, 2026, 7:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f16753f4f88190940e53312aff4333 |
completed | April 29, 2026, 2:05 a.m. |
Created at: April 8, 2026, 9:43 p.m.