Triple
T11821759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASL playoffs |
E281153
|
entity |
| Predicate | determineTitle |
P66163
|
FINISHED |
| Object | NASL champion |
—
|
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: NASL champion | Statement: [NASL playoffs, determineTitle, NASL champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: determineTitle Context triple: [NASL playoffs, determineTitle, NASL champion]
-
A.
decidesTitle
Indicates that one entity determines or selects the official title or name assigned to another entity.
-
B.
titleDeciderFor
chosen
Indicates that one entity is responsible for determining or assigning the title associated with another entity.
-
C.
decidingFactorForTitle
Indicates that something serves as the key criterion or primary reason for determining or awarding a particular title.
-
D.
hasTitleFrom
Indicates that one entity holds or uses a title that originates from, or is conferred by, another entity.
-
E.
namedForTitle
Indicates that one entity is named after or in honor of the title (such as a rank, honorific, or formal designation) associated with another entity.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e9c50481909b2287a0b23d2094 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.