Triple
T3070958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midsummer Classic |
E64019
|
entity |
| Predicate | participantSelection |
P30745
|
FINISHED |
| Object | top players from American League |
—
|
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: top players from American League | Statement: [Midsummer Classic, participantSelection, top players from American League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participantSelection Context triple: [Midsummer Classic, participantSelection, top players from American League]
-
A.
participantFrom
chosen
Indicates that a participant originates from, is associated with, or comes out of a specified source, group, or context.
-
B.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
C.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
D.
invitesParticipationOf
Indicates that one entity actively requests or encourages another entity to take part in an activity, event, or process.
-
E.
participant
Indicates that an entity takes part in, is involved in, or plays a role within a specified event, activity, or process.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14b366881908e2ca104e5f38251 |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.