Triple
T6522577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1934 British Empire Games |
E151218
|
entity |
| Predicate | introducedWomenEventsIn |
P71395
|
FINISHED |
| Object | athletics |
—
|
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: athletics | Statement: [1934 British Empire Games, introducedWomenEventsIn, athletics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedWomenEventsIn Context triple: [1934 British Empire Games, introducedWomenEventsIn, athletics]
-
A.
introducedEvent
Indicates that an entity is responsible for bringing an event into existence or initiating it for the first time.
-
B.
famousForEvent
Indicates that an entity is widely known or recognized specifically because of a particular event.
-
C.
hadWomenOrganization
Indicates that an entity was associated with or involved in an organization focused on women or women’s issues.
-
D.
womenMainEventParticipants
Indicates that the referenced entities are participants in a main event specifically designated for women.
-
E.
introductionEvent
Indicates an event in which one entity is formally presented or made known to another entity or audience for the first time.
- F. None of above. chosen
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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad95c2c88190b800aaaa73f99210 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:45 p.m.