Triple
T25556871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AdvoCare V100 Texas Bowl |
E640594
|
entity |
| Predicate | usedAsTitleWhen |
P73954
|
FINISHED |
| Object | Texas Bowl was sponsored by AdvoCare |
—
|
NE NERFINISHED |
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: Texas Bowl was sponsored by AdvoCare | Statement: [AdvoCare V100 Texas Bowl, usedAsTitleWhen, Texas Bowl was sponsored by AdvoCare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsTitleWhen Context triple: [AdvoCare V100 Texas Bowl, usedAsTitleWhen, Texas Bowl was sponsored by AdvoCare]
-
A.
usedAsTitleInFull
Indicates that something functions as a formal title within the complete, official version of a name or designation.
-
B.
usedAsTitleUntil
Indicates that a particular title was held or used by an entity up to (and including or until) a specified end time.
-
C.
usedTitleIn
chosen
Indicates that one entity employed or referenced another entity as a title in some context.
-
D.
usedAsTitleBeforeName
Indicates that a term or phrase functions as a formal title placed immediately before a person's name.
-
E.
usesTitleIn
Indicates that an entity is referred to using a particular title within a specified context or medium.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 3:40 p.m.