Triple
T28408342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aegina (nymph) |
E719598
|
entity |
| Predicate | waterDeityType |
P9989
|
FINISHED |
| Object | river nymph |
—
|
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: river nymph | Statement: [Aegina (nymph), waterDeityType, river nymph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterDeityType Context triple: [Aegina (nymph), waterDeityType, river nymph]
-
A.
sacredWaterBody
Indicates that a water body holds religious or spiritual significance within a belief system or ritual practice.
-
B.
deityCategory
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
-
C.
waterBodySourceTradition
Indicates the tradition, belief system, or cultural practice from which the association or significance of a water body originates.
-
D.
desiredRiverGod
Indicates that an entity wishes to have or gain favor from a particular river god.
-
E.
typeOfDeity
chosen
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 28, 2026, 1:25 a.m.