Triple
T13983373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afterlife |
E336369
|
entity |
| Predicate | hasMottoOrRecurringImage |
P33142
|
FINISHED |
| Object | coyotes as metaphor for danger and guidance |
—
|
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: coyotes as metaphor for danger and guidance | Statement: [Afterlife, hasMottoOrRecurringImage, coyotes as metaphor for danger and guidance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoOrRecurringImage Context triple: [Afterlife, hasMottoOrRecurringImage, coyotes as metaphor for danger and guidance]
-
A.
hasMottoRibbon
Indicates that an entity features or is associated with a ribbon element specifically used to display a motto.
-
B.
mottoPresent
Indicates that an entity currently has an official motto associated with it.
-
C.
hasMottoLikeFunction
chosen
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
D.
hasMottoContext
Indicates that an entity’s motto is associated with or applies within a specific contextual setting or scope.
-
E.
hasMottoInText
Indicates that an entity has a motto expressed in a specific textual form or wording.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ea2e8808190a1203a6386224bd8 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.