Triple
T14995517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleo |
E373949
|
entity |
| Predicate | setAgainstBackdropOf |
P26195
|
FINISHED |
| Object | Mexico City in the early 1970s |
—
|
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: Mexico City in the early 1970s | Statement: [Cleo, setAgainstBackdropOf, Mexico City in the early 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setAgainstBackdropOf Context triple: [Cleo, setAgainstBackdropOf, Mexico City in the early 1970s]
-
A.
formsBackdropOf
chosen
Indicates that one entity serves as the background or setting against which another entity is viewed, occurs, or is presented.
-
B.
positionedAgainst
Indicates that one entity is placed so that it directly faces or is set opposite to another entity, often in close or contacting alignment.
-
C.
hasBackground
Indicates that an entity possesses or is associated with a particular background, such as context, setting, or prior circumstances.
-
D.
isBehind
Indicates that one entity is positioned to the rear of another entity along a relevant spatial or directional axis.
-
E.
imposedOn
Indicates that one party enforces, applies, or places a requirement, burden, or constraint onto another party or 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded718e4288190b5e144f82299a194 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:53 a.m.