Triple
T11881489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Parterre |
E282667
|
entity |
| Predicate | isLocatedBehind |
P49438
|
FINISHED |
| Object | Schönbrunn Palace main building |
—
|
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: Schönbrunn Palace main building | Statement: [Great Parterre, isLocatedBehind, Schönbrunn Palace main building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedBehind Context triple: [Great Parterre, isLocatedBehind, Schönbrunn Palace main building]
-
A.
isBehind
Indicates that one entity is positioned to the rear of another entity along a relevant spatial or directional axis.
-
B.
locatedBehind
chosen
Indicates that one entity is positioned at the rear of or on the far side of another entity along a given viewing or reference direction.
-
C.
installedInFrontOf
Indicates that one object has been placed or mounted so that it is positioned directly in front of another object.
-
D.
locatedAfter
Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
-
E.
isAt
Indicates that one entity is located at or present in the place or position 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d39d2934819093b9f7006f45e5cb |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.