Triple
T32514019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springfield Heights Institute of Technology |
E831010
|
entity |
| Predicate | hasFictionalMotto |
P141177
|
FINISHED |
| Object | non-notable or unspecified in canon |
—
|
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: non-notable or unspecified in canon | Statement: [Springfield Heights Institute of Technology, hasFictionalMotto, non-notable or unspecified in canon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalMotto Context triple: [Springfield Heights Institute of Technology, hasFictionalMotto, non-notable or unspecified in canon]
-
A.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
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.
definesMotto
Indicates that one entity establishes or specifies the official motto associated with another entity.
-
E.
mottoIncluded
chosen
Indicates that a motto is present as part of, or associated with, the referenced 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 1, 2026, 1 a.m.