Triple
T31614538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | smoke paintings |
E806719
|
entity |
| Predicate | canBeDocumentedBy |
P194862
|
FINISHED |
| Object | photography |
—
|
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: photography | Statement: [smoke paintings, canBeDocumentedBy, photography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeDocumentedBy Context triple: [smoke paintings, canBeDocumentedBy, photography]
-
A.
publiclyDocumentedBy
Indicates that information about an entity is recorded and made publicly accessible through a specified documenting source or agent.
-
B.
documentedUsing
Indicates that something is recorded, described, or specified by means of a particular document, tool, or documentation method.
-
C.
documentedThrough
Indicates that something is recorded, evidenced, or made known by means of a specific document or documentation process.
-
D.
hasDocumentationAt
Indicates that something is documented or described in a specific document, file, or location.
-
E.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
- F. None of above. chosen
Provenance (4 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
| PDg | Predicate description generation | batch_69fd8ccaee848190acd59d7d643ad062 |
completed | May 8, 2026, 7:12 a.m. |
Created at: April 30, 2026, 10:38 p.m.