Triple
T30671371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koṇāgamana Buddha |
E780800
|
entity |
| Predicate | worldSystem |
P48366
|
FINISHED |
| Object | previous world-cycle |
—
|
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: previous world-cycle | Statement: [Koṇāgamana Buddha, worldSystem, previous world-cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldSystem Context triple: [Koṇāgamana Buddha, worldSystem, previous world-cycle]
-
A.
worldType
Indicates the classification or category of world or environment that an entity is associated with.
-
B.
worldName
Indicates that an entity has or is associated with a specific world’s name.
-
C.
cosmologicalSystem
chosen
Indicates a relationship in which entities are organized or interact as part of a larger cosmological structure or system (such as a universe, galaxy, or other large-scale cosmic arrangement).
-
D.
capitalPlanet
Indicates that one planet serves as the capital world or primary governing center for another entity (such as a political or administrative body).
-
E.
worldParallels
Indicates that one world, scenario, or context runs in parallel to another, sharing similar structures, events, or conditions without being identical.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 29, 2026, 8:32 p.m.