Triple
T2020800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980 U.S. Olympic ice hockey team |
E44098
|
entity |
| Predicate | famousCall |
P34555
|
FINISHED |
| Object | “Do you believe in miracles? Yes!” |
—
|
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: “Do you believe in miracles? Yes!” | Statement: [1980 U.S. Olympic ice hockey team, famousCall, “Do you believe in miracles? Yes!”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousCall Context triple: [1980 U.S. Olympic ice hockey team, famousCall, “Do you believe in miracles? Yes!”]
-
A.
famousInitiate
Indicates that an entity initiates or starts an action, event, or process in a way that is widely recognized or notable.
-
B.
nowCalled
Indicates that an entity previously known by one name is currently referred to by a different name.
-
C.
popularName
Indicates that the object is a commonly used or widely recognized name or nickname for the subject.
-
D.
callsFor
Indicates that one entity requires, demands, or requests the occurrence of another action, condition, or entity.
-
E.
hasNotablePersonWithSurname
Indicates that an entity is associated with at least one notable person who bears a specified surname.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8d0bcbc8190bbbb726ecae1c51b |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb83e7888819096dc40275c77daff |
completed | March 7, 2026, 5:31 a.m. |
Created at: March 4, 2026, 7:38 p.m.