Triple
T30625064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaivasvata Manvantara |
E779552
|
entity |
| Predicate | hasWorldOrder |
P48183
|
FINISHED |
| Object | present world order |
—
|
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: present world order | Statement: [Vaivasvata Manvantara, hasWorldOrder, present world order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorldOrder Context triple: [Vaivasvata Manvantara, hasWorldOrder, present world order]
-
A.
hasWorldStructure
chosen
Indicates that an entity possesses or is characterized by a particular overall world-level organization, framework, or structural configuration.
-
B.
hasWorldNumber
Indicates that an entity is associated with a specific world identified by a particular number.
-
C.
hasWorld
Indicates that an entity possesses, is associated with, or encompasses a particular world or global context.
-
D.
hasViewOnWorld
Indicates that an entity holds a particular perspective, opinion, or interpretation regarding the world or reality as a whole.
-
E.
hasWorldCount
Indicates that an entity is associated with a specific number of worlds.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 29, 2026, 8:27 p.m.