Triple
T27990394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearblossom Hwy., 11–18th April 1986, #2 |
E706853
|
entity |
| Predicate | made from |
P151192
|
FINISHED |
| Object | multiple color photographs |
—
|
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: multiple color photographs | Statement: [Pearblossom Hwy., 11–18th April 1986, #2, made from, multiple color photographs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: made from Context triple: [Pearblossom Hwy., 11–18th April 1986, #2, made from, multiple color photographs]
-
A.
madeWith
Indicates that one entity is created, produced, or constructed using another entity as a material, ingredient, or component.
-
B.
madeBy
Indicates that something is created, produced, or brought into existence by a particular agent or source.
-
C.
isProducedFrom
chosen
Indicates that something is created, generated, or derived from a specified source or input.
-
D.
builtFrom
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
-
E.
materialFormedIn
Indicates that a material is created, produced, or formed within a specified process, environment, 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63ba6c208819083e11be320cd6807 |
completed | May 2, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:49 p.m.