Triple
T859834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Yantra |
E18573
|
entity |
| Predicate | hasGeometricNature |
P2435
|
FINISHED |
| Object | sacred geometry |
—
|
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: sacred geometry | Statement: [Sri Yantra, hasGeometricNature, sacred geometry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeometricNature Context triple: [Sri Yantra, hasGeometricNature, sacred geometry]
-
A.
isGeometric
Indicates that something has the properties or form of a geometric figure, pattern, or structure.
-
B.
hasGeodesics
Indicates that the subject possesses or is characterized by geodesic paths, typically representing shortest or straightest possible routes within a given space or geometry.
-
C.
hasGeographyCharacteristic
Indicates that an entity possesses a specific geographical feature, property, or attribute.
-
D.
hasCurvatureInvariant
Indicates that one entity possesses a specific curvature-related invariant property or value associated with its geometric or mathematical structure.
-
E.
hasNature
chosen
Indicates that something possesses, exhibits, or is characterized by a particular inherent quality, essence, or fundamental type.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac50e5ec81908ac0c4b7123b4ebb |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa84835081908aaf98b10656d7d6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.