Triple
T6523761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 MLS Cup |
E151249
|
entity |
| Predicate | aggregateTitle |
P71403
|
FINISHED |
| Object | completed domestic treble for Toronto FC in 2017 |
—
|
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: completed domestic treble for Toronto FC in 2017 | Statement: [2017 MLS Cup, aggregateTitle, completed domestic treble for Toronto FC in 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aggregateTitle Context triple: [2017 MLS Cup, aggregateTitle, completed domestic treble for Toronto FC in 2017]
-
A.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
B.
higherTitleOf
Indicates that one entity holds a job or position title that is hierarchically superior to the title held by another entity.
-
C.
titles
Indicates that one entity holds a formal title, designation, or name associated with another entity.
-
D.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
E.
titleHierarchy
Indicates a hierarchical relationship between titles, where one title is ranked above or below another in an ordered structure.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad970afc81909d3231203eacf413 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69c69f362ee4819090e8fa48caef7d7d |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 1:45 p.m.