Triple
T21029481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geburah |
E518026
|
entity |
| Predicate | positionOnTreeDiagram |
P142545
|
FINISHED |
| Object | left side of central hexagon |
—
|
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: left side of central hexagon | Statement: [Geburah, positionOnTreeDiagram, left side of central hexagon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnTreeDiagram Context triple: [Geburah, positionOnTreeDiagram, left side of central hexagon]
-
A.
positionOnTreeOfLife
Indicates the relative placement of an entity within the evolutionary hierarchy or branching structure of the tree of life.
-
B.
positionInFamilyTree
Indicates the familial relationship or generational position one person holds relative to another within a family tree.
-
C.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
D.
positionInCascade
Indicates the specific step or level an element occupies within an ordered cascade or sequence of dependent stages.
-
E.
positionDepicted
Indicates that one entity visually represents or depicts the spatial position or placement of another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:55 p.m.