Triple
T19046837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wall Drawing #1 |
E466156
|
entity |
| Predicate | executionSurface |
P134877
|
FINISHED |
| Object | architectural wall |
—
|
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: architectural wall | Statement: [Wall Drawing #1, executionSurface, architectural wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executionSurface Context triple: [Wall Drawing #1, executionSurface, architectural wall]
-
A.
executionSide
Indicates which party or side in a transaction, contract, or interaction is responsible for performing or carrying out the specified action.
-
B.
executionModel
Indicates how a process, task, or operation is carried out or implemented, specifying the underlying method, strategy, or mechanism of its execution.
-
C.
executionEngine
Indicates the mechanism or component responsible for carrying out, managing, or running a defined process, task, or set of operations.
-
D.
executionDevice
Indicates that an entity serves as the instrument, tool, or device used to carry out or execute a particular action or process.
-
E.
trainingSurface
Indicates the surface or environment on which a training activity or practice takes place.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d80466f88190988171920f2be7dc |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4c0fc3c4c8190abbfe06e1bd3325c |
completed | April 19, 2026, 11:48 a.m. |
Created at: April 10, 2026, 12:03 p.m.