Triple
T6649479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allianz Stadium |
E150783
|
entity |
| Predicate | openingMatchResult |
P72056
|
FINISHED |
| Object | 1–1 draw |
—
|
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: 1–1 draw | Statement: [Allianz Stadium, openingMatchResult, 1–1 draw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingMatchResult Context triple: [Allianz Stadium, openingMatchResult, 1–1 draw]
-
A.
openingMatch
Indicates that one entity serves as the initial or first match, game, or contest in a series, event, or competition involving another entity.
-
B.
openingMatchScore
Indicates the degree of similarity or compatibility between an opening (e.g., a position, role, or opportunity) and a given candidate or item, typically expressed as a numeric score.
-
C.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
D.
finalFirstMatchResult
Indicates that the referenced result is the first outcome in a sequence that is considered final or decisive for a given matching process.
-
E.
openingRole
Indicates the functional role or position an entity holds at the initial or starting phase of an event, process, or sequence.
- 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 2:01 p.m.