Triple
T3391107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the One |
E71418
|
entity |
| Predicate | knownBy |
P22660
|
FINISHED |
| Object | mystical union |
—
|
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: mystical union | Statement: [the One, knownBy, mystical union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownBy Context triple: [the One, knownBy, mystical union]
-
A.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
B.
recognizedThrough
Indicates that something becomes known, identified, or acknowledged by means of a particular method, medium, or process.
-
C.
recognizedIn
Indicates that an entity is formally acknowledged, honored, or given recognition within a particular context, setting, or domain.
-
D.
knows
chosen
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
E.
followersKnownAs
Indicates that the followers of an entity are referred to by a particular name or label.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb6682c708190b76a7a16cee7c5aa |
completed | March 8, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.