Triple
T15477860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady of the Sea |
E376830
|
entity |
| Predicate | roleOfReferencedDeity |
P118406
|
FINISHED |
| Object | consort of a high god |
—
|
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: consort of a high god | Statement: [Lady of the Sea, roleOfReferencedDeity, consort of a high god]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfReferencedDeity Context triple: [Lady of the Sea, roleOfReferencedDeity, consort of a high god]
-
A.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
B.
depictedDeity
Indicates that one entity is a deity who is shown or represented in an image, artwork, or visual depiction associated with another entity.
-
C.
attributeOfDeity
Indicates that something is a characteristic, quality, or property belonging to a deity.
-
D.
deityIdentification
Indicates that one entity is identified, recognized, or designated as a deity in relation to another entity or context.
-
E.
representsDeity
Indicates that one entity serves as a symbolic, artistic, or conceptual depiction of a deity associated with another entity.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f88a5dc8190a2d7830748e29180 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded5deee00819099fa3e43313312e1 |
completed | April 15, 2026, 12:03 a.m. |
Created at: April 10, 2026, 3:34 a.m.