Triple
T3140838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gardens of the Palace of Versailles |
E65639
|
entity |
| Predicate | layoutAxis |
P32356
|
FINISHED |
| Object | east–west axis |
—
|
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: east–west axis | Statement: [Gardens of the Palace of Versailles, layoutAxis, east–west axis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layoutAxis Context triple: [Gardens of the Palace of Versailles, layoutAxis, east–west axis]
-
A.
layoutEngine
Indicates the rendering or layout system responsible for arranging and positioning elements within a visual or document structure.
-
B.
horizontalAxis
Indicates that one entity serves as the horizontal reference line or direction along which another entity is oriented, measured, or arranged.
-
C.
usesAxis
chosen
Indicates that one entity employs or relies on another entity as a reference axis or basis for orientation, measurement, or organization.
-
D.
ridgeAxis
Indicates the central line or crest along the top of a ridge that defines its main axis or direction.
-
E.
hasLayout
Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of another 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada57895dc8190bd3d4ef9391973dc |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.