Triple
T31171699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Burns |
E794622
|
entity |
| Predicate | hasLifeGoal |
P116862
|
FINISHED |
| Object | search for his absent father |
—
|
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: search for his absent father | Statement: [Jack Burns, hasLifeGoal, search for his absent father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLifeGoal Context triple: [Jack Burns, hasLifeGoal, search for his absent father]
-
A.
hasPlanningGoal
Indicates that an entity is associated with, or directed toward achieving, a specific planning objective or target state.
-
B.
goalOfLiving
chosen
Indicates that something represents the primary purpose, aim, or ultimate objective guiding a being’s life or existence.
-
C.
hasSpiritualGoal
Indicates that an entity is oriented toward or pursues a particular spiritual aim, purpose, or aspiration.
-
D.
hasPrimaryGoal
Indicates that an entity’s main or most important objective is the specified goal.
-
E.
hasProgramGoal
Indicates that an entity (such as a program or initiative) is associated with a specific intended goal or objective it aims to achieve.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 29, 2026, 9:07 p.m.