Triple
T8209869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soccer Bowl |
E191785
|
entity |
| Predicate | decidesTitleFor |
P10211
|
FINISHED |
| Object | NASL season |
—
|
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 season | Statement: [Soccer Bowl, decidesTitleFor, NASL season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidesTitleFor Context triple: [Soccer Bowl, decidesTitleFor, NASL season]
-
A.
decidesTitle
Indicates that one entity determines or selects the official title or name assigned to another entity.
-
B.
titleDeciderFor
Indicates that one entity is responsible for determining or assigning the title associated with another entity.
-
C.
decidesTitleForSeason
chosen
Indicates that an entity has the authority or responsibility to choose or determine the title for a particular season.
-
D.
createdTitleBy
Indicates that a title (such as a work, document, or creative piece) was created by a specific agent or creator.
-
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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76dd881c8190adcbeb2f33d3295c |
completed | March 31, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:44 p.m.