Triple
T14015611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | modern pentathlon |
E337196
|
entity |
| Predicate | fencingFormat |
P2673
|
FINISHED |
| Object | one-touch épée |
—
|
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: one-touch épée | Statement: [modern pentathlon, fencingFormat, one-touch épée]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fencingFormat Context triple: [modern pentathlon, fencingFormat, one-touch épée]
-
A.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
homeFencingVenue
Indicates that a specified venue serves as the primary or regular location where an entity (such as a team or fencer) hosts its fencing activities or events.
-
C.
tourFormat
Indicates the specific structure, style, or type of a tour associated with an entity.
-
D.
playedFormat
Indicates that an entity (such as a game, show, or media content) is or was presented, delivered, or experienced in a particular format (such as digital, physical, live, or specific media type).
-
E.
spectatorFormat
Indicates the format or mode in which an entity is viewed or experienced by spectators or observers.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f396b648190927e5718c3bb6511 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.