Triple
T17096508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahabharata tradition in Java |
E414863
|
entity |
| Predicate | includesLocalDeities |
P116883
|
FINISHED |
| Object | Javanese guardian spirits |
—
|
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: Javanese guardian spirits | Statement: [Mahabharata tradition in Java, includesLocalDeities, Javanese guardian spirits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesLocalDeities Context triple: [Mahabharata tradition in Java, includesLocalDeities, Javanese guardian spirits]
-
A.
sharesDeitiesWith
Indicates that two entities have one or more deities in common within their respective religious or mythological systems.
-
B.
hasDeities
chosen
Indicates that one entity possesses, is associated with, or is served by one or more deities.
-
C.
hasNumberOfDeities
Indicates the specific count of deities associated with an entity, such as a religion, mythology, or belief system.
-
D.
otherDeity
Indicates that one deity is distinct from and not identical to another deity within a given context or system.
-
E.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfdc9c88190b4e75bbdf4105c1e |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.