Triple
T34468295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jambūdvīpaprajñapti |
E884833
|
entity |
| Predicate | worldPosition |
P60416
|
FINISHED |
| Object | center of Madhyaloka |
—
|
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: center of Madhyaloka | Statement: [Jambūdvīpaprajñapti, worldPosition, center of Madhyaloka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldPosition Context triple: [Jambūdvīpaprajñapti, worldPosition, center of Madhyaloka]
-
A.
positionInWorlds
chosen
Indicates that an entity occupies specific spatial coordinates or locations within one or more distinct worlds or environments.
-
B.
relationshipToWorld
Indicates how an entity is connected or related to the broader world or external environment.
-
C.
positionRelativeToEarth
Indicates the spatial position or orientation of an entity in relation to the Earth as a reference frame.
-
D.
positionRelativeToSurface
Indicates how an entity is spatially located or oriented with respect to a reference surface.
-
E.
worldFileLocation
Indicates the file path or storage location where a particular world or environment configuration is saved.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 1, 2026, 2:01 a.m.