Triple
T21029397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kether |
E518025
|
entity |
| Predicate | roleInTreeOfLife |
P109646
|
FINISHED |
| Object | divine crown |
—
|
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: divine crown | Statement: [Kether, roleInTreeOfLife, divine crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTreeOfLife Context triple: [Kether, roleInTreeOfLife, divine crown]
-
A.
treeOfLife
chosen
Indicates a relationship where one entity represents or serves as a foundational source, lineage, or central organizing structure for the existence, development, or diversity of another.
-
B.
biologicalRole
Indicates the functional role or purpose that one biological entity has in relation to another or within a biological process.
-
C.
roleInNomenclature
Indicates the specific function or status an entity holds within a particular naming or classification system.
-
D.
positionOnTreeOfLife
Indicates the relative placement of an entity within the evolutionary hierarchy or branching structure of the tree of life.
-
E.
taxonOf
Indicates that one entity is the taxonomic group (taxon) to which the other entity belongs.
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc7fd3ec81908ac237047f9b0d7a |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.