Triple
T16810381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hulkster |
E408591
|
entity |
| Predicate | hasAssociatedMotto |
P29651
|
FINISHED |
| Object | Train, say your prayers, and eat your vitamins |
—
|
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: Train, say your prayers, and eat your vitamins | Statement: [The Hulkster, hasAssociatedMotto, Train, say your prayers, and eat your vitamins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedMotto Context triple: [The Hulkster, hasAssociatedMotto, Train, say your prayers, and eat your vitamins]
-
A.
hasMottoDepiction
Indicates that something visually represents or depicts the motto associated with an entity.
-
B.
usesMotto
chosen
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
C.
hasMottoAuthority
Indicates that an entity has the official power or right to establish, approve, or oversee the use of a motto for another 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.
hasPartInMotto
Indicates that something is included as a component or element within a 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cf680c8190bcd640570c524918 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.