Triple
T38096293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weighing of the Heart scene |
E951250
|
entity |
| Predicate | locationInMythology |
P20384
|
FINISHED |
| Object | Hall of Two Truths |
E290572
|
NE 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: Hall of Two Truths | Statement: [Weighing of the Heart scene, locationInMythology, Hall of Two Truths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInMythology Context triple: [Weighing of the Heart scene, locationInMythology, Hall of Two Truths]
-
A.
mythologicalLocation
chosen
Indicates that the subject is a place or setting that exists within mythology, legends, or folklore rather than in historical or physical reality.
-
B.
positionOnMyth
Indicates the relative stance or viewpoint an entity holds regarding a particular myth.
-
C.
typeOfLocationInMyths
Indicates that a location is classified by the kind of place it is within the context of myths or mythological narratives.
-
D.
relatedMythicalPlace
Indicates that one entity has an association or connection with a mythical or legendary place in relation to the other entity.
-
E.
mythicalBirthplaceOf
Indicates the legendary or mythological location where an entity is said to have originated or been born.
- F. None of above.
Provenance (4 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a417119da708190a9e0a516c71fd333 |
completed | June 28, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.