Triple
T6393257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dictys |
E143878
|
entity |
| Predicate | foundAfter |
P70361
|
FINISHED |
| Object | Perseus and Danaë washed ashore |
—
|
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: Perseus and Danaë washed ashore | Statement: [Dictys, foundAfter, Perseus and Danaë washed ashore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundAfter Context triple: [Dictys, foundAfter, Perseus and Danaë washed ashore]
-
A.
finds
Indicates that one entity discovers, locates, or comes upon another entity, often as the result of a search or encounter.
-
B.
founds
Indicates that an entity establishes or creates an organization, institution, settlement, or similar entity, typically as its originator.
-
C.
containsFinding
Indicates that one entity includes, encompasses, or holds a particular finding as part of its content or results.
-
D.
locatedAfter
Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
-
E.
foundInVolume
Indicates that one entity is physically or logically contained within, or occurs in, a specific volume (such as a book volume, data volume, or bounded collection).
- 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_69c008db906c819096f3597d55d95432 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0687f5c6c81909c835329c996b311 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:34 p.m.