Triple
T18748704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Garden |
E458468
|
entity |
| Predicate | hasLayoutPrinciple |
P47536
|
FINISHED |
| Object | axial 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: axial symmetry | Statement: [Long Garden, hasLayoutPrinciple, axial symmetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLayoutPrinciple Context triple: [Long Garden, hasLayoutPrinciple, axial symmetry]
-
A.
hasLayout
Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of another entity.
-
B.
basedOnLayout
Indicates that one entity is derived from, structured according to, or determined by the layout or spatial arrangement defined by another entity.
-
C.
usesPrinciple
Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
-
D.
implementsPrinciple
chosen
Indicates that an entity applies, follows, or puts into practice a specified principle in its design, behavior, or operation.
-
E.
hasPrincipleDefinition
Indicates that something serves as the primary or authoritative definition of a given concept or term.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579e9903c81908180c46012bd0948 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.