Triple
T2410281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marsyas |
E50371
|
entity |
| Predicate | installationSpace |
P39280
|
FINISHED |
| Object | industrial-scale gallery space |
—
|
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: industrial-scale gallery space | Statement: [Marsyas, installationSpace, industrial-scale gallery space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installationSpace Context triple: [Marsyas, installationSpace, industrial-scale gallery space]
-
A.
installedAt
Indicates that something has been set up, placed, or put into operation at a specific location or site.
-
B.
installedInstrument
Indicates that one entity has placed or set up another entity as an instrument or device for use in a particular context or system.
-
C.
installedBy
Indicates that one entity was set up, put in place, or made operational through the actions or intervention of another entity.
-
D.
installationMedia
Indicates that something serves as or is used as the medium (such as a disk, image, or package) through which a software or system is installed.
-
E.
requiresInstallation
Indicates that one entity must be installed or set up before the other can be used or become operational.
- 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_69a88b0339a88190a1207333cd271cc9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abceab9ce881909ae0a2f34515c11e |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5a530e8819094105aa92dfaf6b3 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abceaa42b88190a790355100fede3d |
completed | March 7, 2026, 7:07 a.m. |
Created at: March 4, 2026, 7:58 p.m.