Triple
T7900352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Story Sunlight |
E183434
|
entity |
| Predicate | depictsArchitectureType |
P4631
|
FINISHED |
| Object | American house |
—
|
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: American house | Statement: [Second Story Sunlight, depictsArchitectureType, American house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsArchitectureType Context triple: [Second Story Sunlight, depictsArchitectureType, American house]
-
A.
renderingArchitecture
Indicates the specific rendering system or framework used to generate visual output for a given entity or environment.
-
B.
architectureType
chosen
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
C.
architecturalIllustrationsBy
Indicates a relationship where one entity has produced or created architectural illustrations for another entity.
-
D.
architecturalWork
Indicates that one entity is an architectural creation (such as a building or structure) designed or realized by another entity.
-
E.
depictionType
Indicates the specific manner or style in which something is visually represented or depicted.
- 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a3dc2208190a6fea93b60b8daca |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:02 p.m.