Triple
T16898434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AD Alcorcón |
E424369
|
entity |
| Predicate | notableMatchResult |
P1706
|
FINISHED |
| Object | 4–0 home win over Real Madrid |
—
|
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: 4–0 home win over Real Madrid | Statement: [AD Alcorcón, notableMatchResult, 4–0 home win over Real Madrid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMatchResult Context triple: [AD Alcorcón, notableMatchResult, 4–0 home win over Real Madrid]
-
A.
notableMatch
Indicates that there exists a particularly significant or noteworthy match or pairing between the related entities.
-
B.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
C.
notableMatchVenueFor
Indicates that a venue is notably associated with hosting a particular match or game.
-
D.
notableOutcome
chosen
Indicates that an action, event, or entity leads to or is associated with a significant, noteworthy result or consequence.
-
E.
notablePlay
Indicates that a particular play is especially famous, significant, or noteworthy in relation to the entity it is associated with.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8d98c308190bcc0adc7797d1f40 |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.