Triple
T22976685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ree Dolly |
E571338
|
entity |
| Predicate | centralGoal |
P150465
|
FINISHED |
| Object | to find her missing father Jessup Dolly |
—
|
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: to find her missing father Jessup Dolly | Statement: [Ree Dolly, centralGoal, to find her missing father Jessup Dolly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralGoal Context triple: [Ree Dolly, centralGoal, to find her missing father Jessup Dolly]
-
A.
secondaryGoal
Indicates that something serves as a subordinate or supporting objective in addition to a primary goal.
-
B.
initialGoal
Indicates that something represents the first or starting objective or target in a sequence of goals.
-
C.
coreGoalTaught
Indicates that a fundamental or primary goal is explicitly taught or conveyed to someone.
-
D.
strategicGoal
Indicates that one entity represents a long-term objective or desired outcome that another entity is intentionally aiming to achieve or align actions toward.
-
E.
legacyGoal
Indicates that an entity has a long-term, enduring objective or impact it aims to leave behind beyond its immediate actions or existence.
- F. None of above. chosen
Provenance (4 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182369b548190a6630655a6e0bb39 |
completed | April 29, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:48 p.m.