Triple
T31606331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Last City |
E806498
|
entity |
| Predicate | reflectsWork |
P922
|
FINISHED |
| Object | Architecture as Autobiography |
—
|
NE NERFINISHED |
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: Architecture as Autobiography | Statement: [The Last City, reflectsWork, Architecture as Autobiography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsWork Context triple: [The Last City, reflectsWork, Architecture as Autobiography]
-
A.
reflectsOnWork
Indicates that an entity engages in thoughtful consideration or evaluation of their own work or work-related activities.
-
B.
showsWorkOf
Indicates that one entity presents, exhibits, or displays the work or creations produced by another entity.
-
C.
ownsWork
Indicates that one entity has legal ownership or proprietary rights over a particular work or creation.
-
D.
reflects
Indicates that one entity (often a surface, medium, or representation) throws back, mirrors, or otherwise shows an image, property, or state of another entity.
-
E.
associatedWork
chosen
Indicates that there exists a related or connected work (such as a publication, creative piece, or project) that is meaningfully linked to the subject.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:34 p.m.