Triple
T7693672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soul of the World |
E174311
|
entity |
| Predicate | goalOfInteraction |
P64674
|
FINISHED |
| Object | alignment with Personal Legend |
—
|
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: alignment with Personal Legend | Statement: [Soul of the World, goalOfInteraction, alignment with Personal Legend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfInteraction Context triple: [Soul of the World, goalOfInteraction, alignment with Personal Legend]
-
A.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
B.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
C.
goalDescription
Indicates that an entity expresses, specifies, or provides a textual description of a goal or intended outcome associated with another entity or activity.
-
D.
goals
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
-
E.
allegedGoal
Indicates that one entity is claimed or reported to have the goal or intended objective of another entity, without asserting that the goal is actually true.
- 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_69c6995966348190939e6c37ba272c06 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c706d1f0208190bc5b695aa5736244 |
completed | March 27, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69c70163dea88190ae729df50e63dfd7 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:02 p.m.