Triple
T31394247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ida Ilsted |
E800820
|
entity |
| Predicate | typicalPoseInDepictions |
P15582
|
FINISHED |
| Object | seen from behind |
—
|
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: seen from behind | Statement: [Ida Ilsted, typicalPoseInDepictions, seen from behind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPoseInDepictions Context triple: [Ida Ilsted, typicalPoseInDepictions, seen from behind]
-
A.
showsPose
chosen
Indicates that one entity displays or presents a particular pose or bodily posture of another entity.
-
B.
typicalPoseHoldDuration
Indicates the usual length of time that an entity maintains a particular pose before changing it.
-
C.
typicalFigure
Indicates that one entity serves as a standard or representative example (a typical instance) of the other entity.
-
D.
positionDepicted
Indicates that one entity visually represents or depicts the spatial position or placement of another entity.
-
E.
typicalPositioning
Indicates the usual or characteristic spatial arrangement or placement of one entity relative to another or within a given context.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:19 p.m.