Triple
T2790705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Recopa Sudamericana |
E61921
|
entity |
| Predicate | hasHomeAndAwayLegs |
P39328
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Recopa Sudamericana, hasHomeAndAwayLegs, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeAndAwayLegs Context triple: [Recopa Sudamericana, hasHomeAndAwayLegs, true]
-
A.
hasTourLeg
Indicates that a specific segment or leg is part of, or associated with, a larger tour or journey.
-
B.
hasHomeAndAwayFormat
chosen
Indicates that a competition, match, or series is structured with both home and away legs or fixtures between the same opponents.
-
C.
hasDomesticFlights
Indicates that an airline or airport operates flights within the same country, connecting domestic destinations.
-
D.
hasCityPair
Indicates a relationship that links two cities considered as a connected or associated pair, often for purposes such as travel, trade, or comparison.
-
E.
hasCodeShareOrInterline
Indicates that there exists a codeshare or interline agreement relationship between the referenced transportation services or carriers.
- 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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdeea881481908d759c72798a50fb |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd025c948190a97dd961a9592bac |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.