Triple
T5065493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ogden Codman Jr. |
E114132
|
entity |
| Predicate | preferredDesignPrinciple |
P532
|
FINISHED |
| Object | symmetry |
—
|
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: symmetry | Statement: [Ogden Codman Jr., preferredDesignPrinciple, symmetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preferredDesignPrinciple Context triple: [Ogden Codman Jr., preferredDesignPrinciple, symmetry]
-
A.
usesPrinciple
Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
-
B.
implementsPrinciple
Indicates that an entity applies, follows, or puts into practice a specified principle in its design, behavior, or operation.
-
C.
typeOfPrinciples
Indicates a relationship where one entity specifies the kind or category of principles that another entity embodies, uses, or is governed by.
-
D.
designPhilosophy
chosen
Indicates the guiding principles, values, or conceptual approach that shape how something is designed or created.
-
E.
reinforcedPrinciple
Indicates that one entity has strengthened, supported, or validated a principle associated with another entity, making that principle more firmly established or accepted.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7478f7988190bc0473e8af055147 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.