Triple
T1278576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oceanids |
E27270
|
entity |
| Predicate | typeOfMythologicalGroup |
P28328
|
FINISHED |
| Object | collective of individual named nymphs |
—
|
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: collective of individual named nymphs | Statement: [Oceanids, typeOfMythologicalGroup, collective of individual named nymphs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMythologicalGroup Context triple: [Oceanids, typeOfMythologicalGroup, collective of individual named nymphs]
-
A.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
B.
hasDeityGroup
Indicates a relationship where an entity is associated with, or belongs to, a particular group or pantheon of deities.
-
C.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
D.
mythologicalGeneration
Indicates a generational relationship in mythology, where one mythological being or group descends from or follows another in a lineage or succession.
-
E.
hasMythType
Indicates that an entity is associated with or classified under a particular type or category of myth.
- F. None of above. chosen
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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c31400c08190a07ccb736df3bf54 |
completed | March 1, 2026, 10:52 p.m. |
Created at: March 1, 2026, 7:50 p.m.