Triple
T8041760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady of Elche |
E187455
|
entity |
| Predicate | dateReturned |
P46980
|
FINISHED |
| Object | 1941 |
—
|
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: 1941 | Statement: [Lady of Elche, dateReturned, 1941]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateReturned Context triple: [Lady of Elche, dateReturned, 1941]
-
A.
dateOfReturnAsResidence
Indicates the date on which an entity returned to a particular place to resume or establish it as their residence.
-
B.
wasReturnedTo
Indicates that an entity was sent or brought back to a previous owner, location, or state after having been away or removed.
-
C.
wasReturnedIn
chosen
Indicates that an item previously taken or sent was brought or sent back to its original source or owner at a specific time or in a specific context.
-
D.
dateReceived
Indicates the point in time when something (such as a message, item, or document) was received by a recipient.
-
E.
deliveryDate
Indicates the specific date on which a product, service, or item is scheduled or expected to be delivered.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f1e98508190a29a7bb5055f8ba0 |
completed | March 31, 2026, 3:27 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:23 p.m.