Triple
T16212971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltimore Ravens Ring of Honor |
E393511
|
entity |
| Predicate | inductionEvent |
P19113
|
FINISHED |
| Object | ceremony held at M&T Bank Stadium |
—
|
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: ceremony held at M&T Bank Stadium | Statement: [Baltimore Ravens Ring of Honor, inductionEvent, ceremony held at M&T Bank Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inductionEvent Context triple: [Baltimore Ravens Ring of Honor, inductionEvent, ceremony held at M&T Bank Stadium]
-
A.
eventIn
chosen
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
B.
introducedEvent
Indicates that an entity is responsible for bringing an event into existence or initiating it for the first time.
-
C.
introductionEvent
Indicates an event in which one entity is formally presented or made known to another entity or audience for the first time.
-
D.
inspiredEvent
Indicates that one event served as the motivation, cause, or creative stimulus for another event to occur or be conceived.
-
E.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f2c1288190bfaed49c364bfa22 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.