Triple
T19166298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wall Drawing #51 |
E469190
|
entity |
| Predicate | installationVariable |
P134690
|
FINISHED |
| Object | scale depends on wall dimensions |
—
|
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: scale depends on wall dimensions | Statement: [Wall Drawing #51, installationVariable, scale depends on wall dimensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installationVariable Context triple: [Wall Drawing #51, installationVariable, scale depends on wall dimensions]
-
A.
installationCommand
Indicates the command or set of commands used to install a particular software, package, or component.
-
B.
installationForm
Indicates the specific method, configuration, or format in which something is installed or set up.
-
C.
installationContext
Indicates the situational or environmental setting in which an installation occurs or is intended to function.
-
D.
installationSpace
Indicates the physical or virtual area required or designated for installing an object, system, or component.
-
E.
installationMission
Indicates that an entity is assigned the task or mission of installing or setting up another entity.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f15ee064819087f9fd822236298f |
completed | April 20, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:06 p.m.