Triple
T34532522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike I |
E886576
|
entity |
| Predicate | startOfTradition |
P201262
|
FINISHED |
| Object | Mike the Tiger live mascots at LSU |
—
|
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: Mike the Tiger live mascots at LSU | Statement: [Mike I, startOfTradition, Mike the Tiger live mascots at LSU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfTradition Context triple: [Mike I, startOfTradition, Mike the Tiger live mascots at LSU]
-
A.
startPointTradition
chosen
Indicates the origin or initial source from which a particular tradition begins or is established.
-
B.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
-
C.
introducedTradition
Indicates that one entity initiated or brought a particular tradition into practice for another entity or context.
-
D.
establishedTradition
Indicates that something has become a customary, long-standing practice or convention that is regularly followed within a group, culture, or context.
-
E.
mainTradition
Indicates that one entity represents the primary or dominant tradition 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0039c2d5d48190b8ef2c7ef17d8dc5 |
completed | May 10, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_6a0038e525448190a4c815f51595e78d |
completed | May 10, 2026, 7:51 a.m. |
Created at: May 1, 2026, 2:02 a.m.