Triple
T17002226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mel Allen |
E412474
|
entity |
| Predicate | calledEvent |
P126118
|
FINISHED |
| Object | multiple World Series |
—
|
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: multiple World Series | Statement: [Mel Allen, calledEvent, multiple World Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calledEvent Context triple: [Mel Allen, calledEvent, multiple World Series]
-
A.
calledAs
Indicates that one entity is referred to, named, or addressed by another specific name or label.
-
B.
calledBackBy
Indicates that one entity returns a previous call or contact initiated by another entity.
-
C.
holderCalled
Indicates that one entity, acting as a holder or possessor, initiated a phone call or communication to another entity.
-
D.
calledBy
Indicates that one entity initiates a call or invocation to another entity.
-
E.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d37ec2b48190b4f997899d887ba8 |
completed | April 18, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e378e037c88190935d732e0f10d5d7 |
completed | April 18, 2026, 12:28 p.m. |
Created at: April 10, 2026, 5:32 a.m.