Triple
T9142352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Flood in Greek mythology |
E219359
|
entity |
| Predicate | interpretationOfBones |
P87003
|
FINISHED |
| Object | stones |
—
|
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: stones | Statement: [Great Flood in Greek mythology, interpretationOfBones, stones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interpretationOfBones Context triple: [Great Flood in Greek mythology, interpretationOfBones, stones]
-
A.
interpretedBonesOfMotherAs
Indicates that someone examined their mother’s bones and formed a particular interpretation or understanding of them.
-
B.
numberOfBonesRecovered
Indicates the count of bones that have been found and recovered in relation to a particular subject or event.
-
C.
skeleton
Indicates that one entity serves as the basic structural framework or underlying support for another.
-
D.
archaeologicalIdentification
Indicates the relationship by which an entity is recognized, classified, or confirmed as an archaeological object, feature, or context based on evidence or expert analysis.
-
E.
numberOfUnidentifiedRemains
Indicates the count of human remains that have not yet been identified in a given context or case.
- 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8f5f740819098236ada5b95889d |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3d230881909635b2ccea35cedb |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:19 p.m.