Triple
T21703698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Euro 1968 matches |
E535718
|
entity |
| Predicate | matchSurface |
P144976
|
FINISHED |
| Object | grass |
—
|
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: grass | Statement: [UEFA Euro 1968 matches, matchSurface, grass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchSurface Context triple: [UEFA Euro 1968 matches, matchSurface, grass]
-
A.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
B.
matchType
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
C.
matchResult
Indicates the outcome or final status produced by a particular match or game between participants.
-
D.
matchLevel
Indicates the degree or extent to which two entities correspond, align, or are compatible with each other.
-
E.
matchStructure
Indicates that two entities share the same structural pattern or organization, regardless of their specific content or values.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef9b82901c81909de242c920fbc164 |
completed | April 27, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:46 p.m.