Triple
T9293578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An Andalusian Dog |
E223578
|
entity |
| Predicate | createdByMovement |
P21439
|
FINISHED |
| Object | Spanish surrealists |
—
|
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: Spanish surrealists | Statement: [An Andalusian Dog, createdByMovement, Spanish surrealists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdByMovement Context triple: [An Andalusian Dog, createdByMovement, Spanish surrealists]
-
A.
creatorMovement
chosen
Indicates the artistic, cultural, or intellectual movement with which a work’s creator is associated or from which their work primarily derives.
-
B.
createdBy
Indicates that something was brought into existence, produced, or authored through the actions or efforts of a specific agent or entity.
-
C.
movedBy
Indicates that an entity changes position or location as a result of another entity’s action or influence.
-
D.
createdByAct
Indicates that something came into existence or was produced as the result of a specific act or action.
-
E.
enteredBy
Indicates that one entity has been input, recorded, or submitted into a system, record, or context by another 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0898b3288190a627a58bfd9c57fe |
completed | April 1, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.