Triple
T13815102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | women's 3000 metre relay |
E331992
|
entity |
| Predicate | relayChangeMethod |
P111597
|
FINISHED |
| Object | push relay exchanges between teammates |
—
|
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: push relay exchanges between teammates | Statement: [women's 3000 metre relay, relayChangeMethod, push relay exchanges between teammates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relayChangeMethod Context triple: [women's 3000 metre relay, relayChangeMethod, push relay exchanges between teammates]
-
A.
relayType
Indicates the specific kind or category of relay mechanism or configuration used in a system or connection.
-
B.
relayEvents
Indicates that one entity forwards or passes along events it receives to another entity or system.
-
C.
changesWith
Indicates that one entity varies or is modified in response to changes in another entity.
-
D.
functionChange
Indicates that an entity’s function, role, or operational behavior has been altered from one state or purpose to another.
-
E.
positionChange
Indicates a change in an entity’s spatial or positional state from one location or configuration to another.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02806e148190996f58934e66d7d8 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:12 p.m.