Triple
T869699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Muses |
E18781
|
entity |
| Predicate | conceptualDescendantOf |
P909
|
FINISHED |
| Object | earlier local nymph cults |
—
|
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: earlier local nymph cults | Statement: [the Muses, conceptualDescendantOf, earlier local nymph cults]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conceptualDescendantOf Context triple: [the Muses, conceptualDescendantOf, earlier local nymph cults]
-
A.
ancestorDescribedAs
Indicates that an ancestor is characterized or referred to using a particular description, label, or portrayal.
-
B.
subclassOf
Indicates that one class is a more specific type of another class, inheriting its characteristics as a subset of it.
-
C.
derivedFrom
chosen
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
D.
generalizationOf
Indicates that one entity represents a broader, more general concept or category that subsumes or abstracts over another, more specific entity.
-
E.
inheritedFrom
Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac811e548190a72b7a10b5ea8665 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa89ca008190b50d061ac7fe19f9 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.