Triple
T8004780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 12th Man (Texas A&M) |
E186336
|
entity |
| Predicate | sloganUsage |
P6980
|
FINISHED |
| Object | featured on Texas A&M merchandise |
—
|
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: featured on Texas A&M merchandise | Statement: [12th Man (Texas A&M), sloganUsage, featured on Texas A&M merchandise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sloganUsage Context triple: [12th Man (Texas A&M), sloganUsage, featured on Texas A&M merchandise]
-
A.
sloganUsedIn
chosen
Indicates that a particular slogan is employed or featured within a specific context, such as a campaign, advertisement, or organization.
-
B.
sloganScope
Indicates the contextual scope or domain within which a particular slogan is intended to apply or be used.
-
C.
sloganInspired
Indicates that one slogan was created, influenced, or shaped by ideas, style, or content drawn from another source.
-
D.
sloganCategory
Indicates that a slogan is classified as belonging to a particular category or type.
-
E.
sloganGivenBy
Indicates that a particular slogan is provided, coined, or assigned by a specific 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3cf5fb588190ada4ec7d8087619c |
completed | March 31, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:18 p.m.