Triple
T8380920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4 × 400 metres relay at the 1924 Summer Olympics |
E197684
|
entity |
| Predicate | relayType |
P81752
|
FINISHED |
| Object | long sprint relay |
—
|
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: long sprint relay | Statement: [4 × 400 metres relay at the 1924 Summer Olympics, relayType, long sprint relay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relayType Context triple: [4 × 400 metres relay at the 1924 Summer Olympics, relayType, long sprint relay]
-
A.
receiverType
Indicates the category or classification of the entity that receives something (such as a message, resource, or action) in the relationship.
-
B.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
C.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
D.
linkType
Indicates the specific kind or category of relationship that connects two linked entities.
-
E.
relayTeammate
Indicates that one entity participates as a teammate with another entity in a relay event or relay-style activity.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80c57080819097eef2b7e46eaaee |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76da264881909483b835e1db06da |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6:02 p.m.