Triple
T27869887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITA |
E704462
|
entity |
| Predicate | usedInMatchSchedules |
P180936
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ITA, usedInMatchSchedules, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInMatchSchedules Context triple: [ITA, usedInMatchSchedules, yes]
-
A.
usedInMatch
Indicates that something (such as an item, tactic, or resource) was employed or utilized during a particular match or game.
-
B.
usedInMatchType
Indicates that something (such as a rule, item, or configuration) is applied or relevant within a specific type or category of match.
-
C.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
D.
usedInLeague
Indicates that an entity (such as a team, player, or item) participates or is employed within a particular league.
-
E.
typicalMatchSchedule
Indicates the usual or standard timing and arrangement of when matches are scheduled to occur.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 27, 2026, 6:23 p.m.