Triple
T8173440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norway U18 |
E190880
|
entity |
| Predicate | typeOfMatches |
P10212
|
FINISHED |
| Object | international youth friendlies |
—
|
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: international youth friendlies | Statement: [Norway U18, typeOfMatches, international youth friendlies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMatches Context triple: [Norway U18, typeOfMatches, international youth friendlies]
-
A.
matchTypes
Indicates that two or more entities share the same type or category according to a specified classification.
-
B.
matchType
chosen
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
C.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
D.
finalMatchType
Indicates the specific category or format of the concluding or decisive match in a series or competition.
-
E.
featuredMatchType
Indicates the specific category or kind of match that is highlighted or given special prominence.
- 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb48092b348190a37cb3746a434094 |
completed | March 31, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:39 p.m.