Triple
T14985007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miller House |
E373677
|
entity |
| Predicate | planForm |
P8653
|
FINISHED |
| Object | rectilinear plan |
—
|
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 plan | Statement: [Miller House, planForm, rectilinear plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planForm Context triple: [Miller House, planForm, rectilinear plan]
-
A.
plan
Indicates that an entity intends or arranges for a future action or sequence of actions to occur.
-
B.
planType
chosen
Indicates the specific category or kind of plan associated with an entity, such as its level, structure, or intended use.
-
C.
planning
Indicates that an entity is engaged in organizing or devising a future action, event, or course of behavior involving another entity or entities.
-
D.
planOutcome
Indicates the result or consequence that is expected or produced by a given plan.
-
E.
urbanPlanningForm
Indicates the specific type or structure of urban planning approach applied to a place or development.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6ff4a7c8190ab7554f3a1a09b67 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:52 a.m.