Triple
T11776332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miracle of Bern |
E280027
|
entity |
| Predicate | hasEarlyScoreline |
P80730
|
FINISHED |
| Object | Hungary leading 2–0 |
—
|
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: Hungary leading 2–0 | Statement: [Miracle of Bern, hasEarlyScoreline, Hungary leading 2–0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarlyScoreline Context triple: [Miracle of Bern, hasEarlyScoreline, Hungary leading 2–0]
-
A.
hasEarlyCenter
Indicates that an entity possesses or is associated with a primary focal point, hub, or center that occurs or is established earlier than others in time or sequence.
-
B.
hasScoreRecord
chosen
Indicates that an entity is associated with a specific score entry or scoring record.
-
C.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
D.
hasScoredFor
Indicates that one entity has scored points, goals, or similar achievements on behalf of another entity, such as a team, organization, or side.
-
E.
isEarlyHitFor
Indicates that one entity is an initial or precursor success, discovery, or recognition that occurs early in relation to another entity.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
Created at: April 8, 2026, 9:42 p.m.