Triple
T31885041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMF |
E813984
|
entity |
| Predicate | eventFormatOrganized |
P24926
|
FINISHED |
| Object | World Cup-style bowling tournaments |
—
|
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: World Cup-style bowling tournaments | Statement: [AMF, eventFormatOrganized, World Cup-style bowling tournaments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventFormatOrganized Context triple: [AMF, eventFormatOrganized, World Cup-style bowling tournaments]
-
A.
eventTypeOrganized
Indicates that an entity organized or arranged a specific type or category of event.
-
B.
eventFormat
chosen
Indicates the specific structure, style, or presentation type in which an event is organized or delivered.
-
C.
organisedFor
Indicates that something has been arranged, structured, or coordinated specifically to serve, support, or benefit a particular entity or purpose.
-
D.
eventStartDateOrganized
Indicates the date on which an event is formally scheduled or organized to begin.
-
E.
oftenOrganizedBy
Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 30, 2026, 11:57 p.m.