Triple
T9788473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joy (Inside Out) |
E237545
|
entity |
| Predicate | awarenessOf |
P22660
|
FINISHED |
| Object | Riley's memories |
—
|
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: Riley's memories | Statement: [Joy (Inside Out), awarenessOf, Riley's memories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awarenessOf Context triple: [Joy (Inside Out), awarenessOf, Riley's memories]
-
A.
awareness
Indicates that an entity has conscious knowledge, perception, or understanding of another entity, situation, or fact.
-
B.
usesKnowledgeOf
Indicates that one entity applies or draws upon the knowledge possessed by another entity in performing an action or achieving a result.
-
C.
aimsToRaiseAwarenessOf
Indicates that an entity undertakes actions or efforts with the purpose of increasing others’ knowledge, concern, or recognition of a particular issue, topic, or situation.
-
D.
knows
chosen
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
E.
recognizedFor
Indicates that one entity is acknowledged, credited, or honored for a particular achievement, quality, contribution, or work associated with another 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_69ca84da927881909bda80caecad6010 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda2131164819099e8644e40a3cab6 |
completed | April 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:27 p.m.