Triple
T18201116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernie’s Chalet |
E435786
|
entity |
| Predicate | hasMascotActivity |
P84914
|
FINISHED |
| Object | Bernie Brewer slides down after Brewers home runs |
—
|
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: Bernie Brewer slides down after Brewers home runs | Statement: [Bernie’s Chalet, hasMascotActivity, Bernie Brewer slides down after Brewers home runs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMascotActivity Context triple: [Bernie’s Chalet, hasMascotActivity, Bernie Brewer slides down after Brewers home runs]
-
A.
hasMascot
Indicates that an entity is represented or symbolized by a particular mascot.
-
B.
hasMascotFeature
chosen
Indicates that an entity possesses a specific characteristic, attribute, or element related to a mascot.
-
C.
hasMascotIdentity
Indicates that an entity serves as or possesses the role/identity of a mascot for another entity.
-
D.
isMascot
Indicates that one entity serves as the mascot or symbolic representative for another entity, such as an organization, team, or event.
-
E.
usesLiveMascot
Indicates that an entity employs a real, living mascot (such as an animal or person) to represent or promote itself.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d71f288190918ca78543118bbe |
completed | April 19, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.