Triple
T27961378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | myth of Cupid and Psyche |
E704584
|
entity |
| Predicate | earliestFullSourceDate |
P169271
|
FINISHED |
| Object | 2nd century CE |
—
|
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: 2nd century CE | Statement: [myth of Cupid and Psyche, earliestFullSourceDate, 2nd century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestFullSourceDate Context triple: [myth of Cupid and Psyche, earliestFullSourceDate, 2nd century CE]
-
A.
earliestFullSource
chosen
Indicates that one entity is the earliest (in time or order) complete source or origin for another entity.
-
B.
earliestVersionDate
Indicates the date on which the earliest known or first version of an entity was created, released, or became valid.
-
C.
earliestExtendedSource
Indicates that one entity is the earliest or first-occurring instance among a set of extended sources related to another entity.
-
D.
earliestDate
Indicates the earliest point in time at which an associated event, state, or relationship is considered to begin or be valid.
-
E.
earliestDocumentsDate
Indicates the earliest date on which the associated documents were created, recorded, or became valid.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 7:32 p.m.