Triple
T26067432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Three football series |
E657440
|
entity |
| Predicate | trophyOrTitle |
P2890
|
FINISHED |
| Object | Little Three title |
—
|
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: Little Three title | Statement: [Little Three football series, trophyOrTitle, Little Three title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trophyOrTitle Context triple: [Little Three football series, trophyOrTitle, Little Three title]
-
A.
trophyNameRefersTo
Indicates that a given trophy name refers to, denotes, or is associated with a particular trophy entity.
-
B.
trophyOfficialName
Indicates the official, formally recognized name assigned to a particular trophy.
-
C.
trophy
chosen
Indicates that one entity is a trophy awarded or possessed in relation to another entity, typically as a result of winning or achieving something.
-
D.
trophySignificance
Indicates that one entity (typically a trophy) holds a particular level or type of importance, value, or meaning in relation to another entity.
-
E.
trophyWonWith
Indicates that a particular trophy or award was achieved using, through, or in association with a specified means, tool, team, or context.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:25 p.m.