Triple
T796798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubai World Cup |
E17039
|
entity |
| Predicate | attendanceType |
P2636
|
FINISHED |
| Object | invitation of elite international competitors |
—
|
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: invitation of elite international competitors | Statement: [Dubai World Cup, attendanceType, invitation of elite international competitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attendanceType Context triple: [Dubai World Cup, attendanceType, invitation of elite international competitors]
-
A.
attendance
chosen
Indicates the relationship between an event and the people who are present at or participate in that event.
-
B.
recordAttendance
Indicates that an entity documents or logs the presence or participation of another entity at a specific event, session, or time.
-
C.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
-
D.
attendedBy
Indicates that an event, place, or activity is participated in or visited by a particular person or group.
-
E.
isAt
Indicates that one entity is located at or present in the place or position of another 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7b172e88190a26d31c9075b81fb |
completed | March 1, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69a4a5122a008190b0c621b7bc588d41 |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:38 p.m.