Triple
T34099301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pride of the Buckeyes |
E874518
|
entity |
| Predicate | hasMottoRelatedName |
P176275
|
FINISHED |
| Object | “The Best Damn Band in the Land” |
—
|
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: “The Best Damn Band in the Land” | Statement: [Pride of the Buckeyes, hasMottoRelatedName, “The Best Damn Band in the Land”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoRelatedName Context triple: [Pride of the Buckeyes, hasMottoRelatedName, “The Best Damn Band in the Land”]
-
A.
hasMottoOrAssociation
chosen
Indicates a relationship where an entity is linked to a motto, slogan, or associated phrase that represents or characterizes it.
-
B.
hasMottoSymbol
Indicates that an entity’s motto is represented or accompanied by a particular symbol.
-
C.
hasMottoDepiction
Indicates that something visually represents or depicts the motto associated with an entity.
-
D.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
E.
hasMottoElement
Indicates that something includes a specific phrase or component as part of its motto.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: May 1, 2026, 1:53 a.m.