Triple
T35101382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leda and the Swan |
E1013025
|
entity |
| Predicate | hasLaterReceptionIn |
P188418
|
FINISHED |
| Object | classical art |
—
|
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: classical art | Statement: [Leda and the Swan, hasLaterReceptionIn, classical art]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterReceptionIn Context triple: [Leda and the Swan, hasLaterReceptionIn, classical art]
-
A.
hasReception
Indicates that an entity hosts, includes, or is associated with a reception event (such as a formal gathering or welcoming function).
-
B.
hasLaterRecognition
chosen
Indicates that one entity receives acknowledgment, fame, or formal recognition at a time later than another entity or later than an initial reference point.
-
C.
hasReceiver
Indicates that an entity serves as the recipient or target of something provided, sent, or directed by another entity.
-
D.
hasLaterArrangements
Indicates that there exist subsequent plans, agreements, or arrangements that occur after or supersede earlier ones.
-
E.
hasReviewReception
Indicates that an entity has received a critical or evaluative review describing how it was received or perceived.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:01 p.m.