Triple
T13138500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Photo 51 |
E312147
|
entity |
| Predicate | materialImaged |
P30544
|
FINISHED |
| Object | hydrated DNA fibers |
—
|
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: hydrated DNA fibers | Statement: [Photo 51, materialImaged, hydrated DNA fibers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialImaged Context triple: [Photo 51, materialImaged, hydrated DNA fibers]
-
A.
materialDepicted
chosen
Indicates that a work or representation visually portrays or includes a particular material as part of its subject.
-
B.
material
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
-
C.
texture
Indicates the surface quality or feel of an entity as perceived by touch or appearance, such as being smooth, rough, soft, or coarse.
-
D.
materialEffect
Indicates that one material causes, influences, or brings about a change in the properties, behavior, or state of another material or system.
-
E.
materialOptions
Indicates that there are one or more possible materials that can be chosen or applied in relation to a given entity or 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b6a4348190b9922ed255759078 |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:09 p.m.