Triple
T25689401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pavilion IX |
E644157
|
entity |
| Predicate | positionOnLawn |
P63244
|
FINISHED |
| Object | west side of the Lawn |
—
|
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: west side of the Lawn | Statement: [Pavilion IX, positionOnLawn, west side of the Lawn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnLawn Context triple: [Pavilion IX, positionOnLawn, west side of the Lawn]
-
A.
locationPosed
Indicates that an entity is positioned or situated at a specific location.
-
B.
positionOnEnvironment
chosen
Indicates the spatial placement or location of an entity relative to a surrounding environment or surface.
-
C.
locationOnField
Indicates the specific position or area that an entity occupies on a defined field or playing surface.
-
D.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
E.
positionOnSystem
Indicates the relative location or placement of an entity within a larger structured system or framework.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 21, 2026, 8:14 p.m.