Triple
T14527977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Almost There |
E340827
|
entity |
| Predicate | describesCharacterGoal |
P42284
|
FINISHED |
| Object | opening a restaurant |
—
|
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: opening a restaurant | Statement: [Almost There, describesCharacterGoal, opening a restaurant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesCharacterGoal Context triple: [Almost There, describesCharacterGoal, opening a restaurant]
-
A.
narrativeGoal
chosen
Indicates that one entity has a desired outcome or objective within a story or narrative context that drives their actions or development.
-
B.
goalDescription
Indicates that an entity expresses, specifies, or provides a textual description of a goal or intended outcome associated with another entity or activity.
-
C.
characterMotivation
Indicates the underlying reasons, desires, or goals that drive a character’s actions and decisions within a narrative.
-
D.
motivatedByGoal
Indicates that an action, behavior, or state occurs as a result of an intention to achieve a specific goal or desired outcome.
-
E.
missionOfAntagonist
Indicates the primary goal, plan, or objective that the antagonist is actively pursuing.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea051bc608190ad4d516c5e7bca43 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.