Triple
T33110648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U-18 Baseball World Cup |
E847319
|
entity |
| Predicate | hasMedalAwards |
P89884
|
FINISHED |
| Object | gold, silver, bronze |
—
|
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: gold, silver, bronze | Statement: [U-18 Baseball World Cup, hasMedalAwards, gold, silver, bronze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMedalAwards Context triple: [U-18 Baseball World Cup, hasMedalAwards, gold, silver, bronze]
-
A.
hasMedalCount
Indicates the relationship between an entity and the number of medals it possesses or has been awarded.
-
B.
hasMultipleAwardsIndicatedBy
Indicates that an entity is recognized as having received multiple awards, as evidenced or signaled by a specified source or indicator.
-
C.
hasMedalEquivalent
Indicates that one medal is considered equivalent in value, status, or recognition to another medal.
-
D.
wonMedalAt
Indicates that an entity received a medal as a result of participating in a specific event or competition.
-
E.
hasMedalEvents
chosen
Indicates that an entity has associated events in which medals are or can be awarded.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 1, 2026, 1:27 a.m.