Triple
T17780382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land art |
E443877
|
entity |
| Predicate | usesLocationType |
P104439
|
FINISHED |
| Object | deserts |
—
|
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: deserts | Statement: [Land art, usesLocationType, deserts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLocationType Context triple: [Land art, usesLocationType, deserts]
-
A.
typicalUseLocation
Indicates the usual or most common location where an entity is used or operates.
-
B.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
C.
supportsLocation
Indicates that one entity provides the necessary structure, foundation, or capacity to hold, host, or accommodate another entity at a particular place or position.
-
D.
settingLocationType
chosen
Indicates the type or category of location in which an event, action, or situation takes place.
-
E.
currentLocationType
Indicates the type or category of place where an entity is currently located.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48720734c819085ebe37065b8c8f3 |
completed | April 19, 2026, 7:41 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.