Triple
T13918665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle World |
E334685
|
entity |
| Predicate | hasVerticalAxisRelation |
P112287
|
FINISHED |
| Object | axis mundi |
—
|
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: axis mundi | Statement: [Middle World, hasVerticalAxisRelation, axis mundi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVerticalAxisRelation Context triple: [Middle World, hasVerticalAxisRelation, axis mundi]
-
A.
visualAxisRelation
Indicates a spatial relationship defined by the alignment or orientation of one entity relative to another along a line of sight or visual axis.
-
B.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
C.
hasDimensionAssociation
Indicates an association between an entity and one or more of its dimensions, such as size, length, width, height, or other measurable extents.
-
D.
isMajorAxisFor
Indicates that something serves as the primary or longest axis that defines the main directional or structural orientation of another object or system.
-
E.
hasAxisCount
Indicates that an entity is associated with a specified number of axes.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de272753e48190bc609482635280ff |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:16 p.m.