Triple
T22643407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Situationism |
E558889
|
entity |
| Predicate | viewsUrbanSpaceAs |
P149044
|
FINISHED |
| Object | field for experimental practices |
—
|
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: field for experimental practices | Statement: [Situationism, viewsUrbanSpaceAs, field for experimental practices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsUrbanSpaceAs Context triple: [Situationism, viewsUrbanSpaceAs, field for experimental practices]
-
A.
createdUrbanSpace
Indicates that an entity was responsible for designing, developing, or establishing a particular urban space or built environment.
-
B.
urbanDesign
Indicates the relationship in which an entity is responsible for planning, organizing, or shaping the physical layout and functional structure of urban spaces.
-
C.
cityView
Indicates that one entity offers a view of, or overlooks, a city.
-
D.
isUrbanSee
Indicates a relationship where a location or area is recognized or classified as an urban settlement or city-like environment.
-
E.
hasUrbanDesign
Indicates that an entity possesses or is associated with a specific urban design plan, feature, or configuration.
- 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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703577948190ae044df4f8500bfe |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:05 p.m.