Triple
T6477560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smith House (Darien, Connecticut) |
E146109
|
entity |
| Predicate | geometricForm |
P1464
|
FINISHED |
| Object | rectilinear volumes |
—
|
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: rectilinear volumes | Statement: [Smith House (Darien, Connecticut), geometricForm, rectilinear volumes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geometricForm Context triple: [Smith House (Darien, Connecticut), geometricForm, rectilinear volumes]
-
A.
geometricFunction
Indicates a relationship where one entity serves as a geometric transformation or operation that, when applied, produces or modifies another geometric entity.
-
B.
geometricInterpretation
Indicates a relationship where one entity provides or embodies a geometric meaning, representation, or visualization of another entity.
-
C.
isGeometric
Indicates that something has the properties or form of a geometric figure, pattern, or structure.
-
D.
generalizedForm
Indicates that one entity is a more abstract, generalized version or broader form of another entity.
-
E.
shape
chosen
Indicates that one entity has a particular geometric or physical form characterized by the other entity.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a4ba9588190a965b9e7feb7e598 |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:51 p.m.