Triple
T26023193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisbon Lions Stand |
E647210
|
entity |
| Predicate | associatedMatch |
P44732
|
FINISHED |
| Object | 1967 European Cup Final |
—
|
NE NERFINISHED |
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: 1967 European Cup Final | Statement: [Lisbon Lions Stand, associatedMatch, 1967 European Cup Final]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMatch Context triple: [Lisbon Lions Stand, associatedMatch, 1967 European Cup Final]
-
A.
associatedWithMatch
chosen
Indicates a relationship where an entity is linked or connected to a particular match or matching event.
-
B.
relatedMatchType
Indicates that two entities are connected through a specified type or category of relationship that defines how they are considered related or matched.
-
C.
associatedSingle
Indicates a one-to-one association where an entity is linked to exactly one corresponding related entity.
-
D.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
E.
significantMatch
Indicates that two entities correspond closely or share a notably strong degree of similarity or relevance to each other.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: April 22, 2026, 9:04 a.m.