Triple
T32509085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajak (MCU) |
E830879
|
entity |
| Predicate | changeOfHeart |
P79725
|
FINISHED |
| Object | decides to stop the Emergence |
—
|
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: decides to stop the Emergence | Statement: [Ajak (MCU), changeOfHeart, decides to stop the Emergence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changeOfHeart Context triple: [Ajak (MCU), changeOfHeart, decides to stop the Emergence]
-
A.
hasChangeOfHeartMoment
chosen
Indicates that an entity experiences a significant shift in feelings, beliefs, or intentions, often reversing a prior stance or decision.
-
B.
changesMindAfter
Indicates that one entity revises or reverses a previously held decision, opinion, or intention after another entity’s action, statement, or influence.
-
C.
heartColor
Indicates the color attribute associated with a heart.
-
D.
heartLinkedTo
Indicates a connection or association between two entities that is based on emotional, romantic, or deeply personal bonds.
-
E.
heartShape
Indicates that one entity has a heart-like or heart-shaped form in relation to another entity or context.
- 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_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1 a.m.