Triple
T19083406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosy Cross |
E467083
|
entity |
| Predicate | goalRepresented |
P120603
|
FINISHED |
| Object | attainment of gnosis |
—
|
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: attainment of gnosis | Statement: [Rosy Cross, goalRepresented, attainment of gnosis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalRepresented Context triple: [Rosy Cross, goalRepresented, attainment of gnosis]
-
A.
goalDescription
Indicates that an entity expresses, specifies, or provides a textual description of a goal or intended outcome associated with another entity or activity.
-
B.
goalStructure
Indicates the overarching objective or intended outcome that organizes and guides the structure of related actions, components, or relationships.
-
C.
goalAssociatedWith
chosen
Indicates that a goal is connected or linked to another entity, such as an activity, plan, or outcome, in a way that reflects relevance or influence.
-
D.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
E.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2eab58c8190a987c88d633c92ec |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.