Triple
T38068602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boom Tube |
E950534
|
entity |
| Predicate | associatedWithMythos |
P9595
|
FINISHED |
| Object | Fourth World |
E951170
|
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: Fourth World | Statement: [Boom Tube, associatedWithMythos, Fourth World]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMythos Context triple: [Boom Tube, associatedWithMythos, Fourth World]
-
A.
linkedToMythology
chosen
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
-
B.
sharesMythosWith
Indicates that two entities are associated with, or originate from, the same mythological tradition, narrative system, or shared set of myths.
-
C.
centralMythology
Indicates that one entity serves as a core or defining mythological element within the context or tradition of another entity.
-
D.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
E.
associatedGoddess
Indicates that one entity is recognized as the goddess traditionally linked or connected to another entity (such as a place, concept, or deity).
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
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_6a41852fef9c8190b353b4d36ef3f852 |
completed | June 28, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.