Triple
T1475594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theseus |
E30832
|
entity |
| Predicate | receivedObject |
P4382
|
FINISHED |
| Object | clew of thread from Ariadne |
—
|
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: clew of thread from Ariadne | Statement: [Theseus, receivedObject, clew of thread from Ariadne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedObject Context triple: [Theseus, receivedObject, clew of thread from Ariadne]
-
A.
receivedFor
Indicates that something was obtained, accepted, or taken into possession on behalf of or for the benefit of a specified entity.
-
B.
receives
chosen
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
C.
receivedSentence
Indicates that one entity has been given or accepted a sentence (such as a legal punishment or formal judgment) from another entity or authority.
-
D.
receivedSupportFrom
Indicates that one entity obtained help, resources, or backing from another entity.
-
E.
returnedWith
Indicates that an entity came back or was brought back accompanied by, or in possession of, another specified entity.
- 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c602387c8190b97a20c8e05e3d16 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c484e52c81908948ff8c0a42751b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:11 p.m.