Triple
T15516572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA men’s swimming and diving |
E368848
|
entity |
| Predicate | includesRelay |
P56991
|
FINISHED |
| Object | freestyle 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: freestyle relay | Statement: [NCAA men’s swimming and diving, includesRelay, freestyle relay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRelay Context triple: [NCAA men’s swimming and diving, includesRelay, freestyle relay]
-
A.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
B.
includedBy
chosen
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
-
C.
relayType
Indicates the specific kind or category of relay mechanism or configuration used in a system or connection.
-
D.
isRelatively
Indicates that one entity is being described, measured, or evaluated in relation to another entity or reference point, rather than in absolute terms.
-
E.
supportsRelayAgents
Indicates that one entity is capable of working with or providing functionality for relay agents that forward or mediate communications between other entities.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04033303c8190a87b6384f68a6921 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:02 a.m.