Triple
T34070652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dies |
E873758
|
entity |
| Predicate | cultureOfEquivalent |
P103277
|
FINISHED |
| Object | Greek mythology |
—
|
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: Greek mythology | Statement: [Dies, cultureOfEquivalent, Greek mythology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultureOfEquivalent Context triple: [Dies, cultureOfEquivalent, Greek mythology]
-
A.
hasCulturalEquivalent
chosen
Indicates that one entity has a counterpart in another cultural context that plays a similar role, function, or meaning.
-
B.
culturallySimilarTo
Indicates that two entities share comparable cultural characteristics, practices, or values.
-
C.
equivalentIn
Indicates that two entities are considered logically or functionally the same in meaning, status, or effect within a given context.
-
D.
centralToCultureOf
Indicates that something is a core, defining, and influential element within the culture of a particular group or society.
-
E.
basedInCulture
Indicates that an entity is situated within, originates from, or is fundamentally associated with a particular culture.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:52 a.m.