Triple
T38066044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | men’s 100 metres at the 1932 Summer Olympics |
E950471
|
entity |
| Predicate | heatsHeldOn |
P9394
|
FINISHED |
| Object | 1932-07-31 |
—
|
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: 1932-07-31 | Statement: [men’s 100 metres at the 1932 Summer Olympics, heatsHeldOn, 1932-07-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heatsHeldOn Context triple: [men’s 100 metres at the 1932 Summer Olympics, heatsHeldOn, 1932-07-31]
-
A.
areHeldIn
Indicates that events, activities, or objects take place or are located within a particular venue, container, or setting.
-
B.
oftenHeldAs
Indicates that one entity is frequently regarded, considered, or believed to be in a particular way with respect to another entity or property.
-
C.
heldOf
Indicates that something is possessed, controlled, or kept by a particular entity.
-
D.
wasHeldUnder
Indicates that an event, activity, or state took place while being subject to the authority, control, jurisdiction, or auspices of a particular entity or condition.
-
E.
heldOn
chosen
Indicates that an event or activity takes place at a specific time, date, or occasion.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:21 p.m.