Triple
T2686460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawa Mahal |
E57494
|
entity |
| Predicate | floorAccess |
P41512
|
FINISHED |
| Object | upper floors accessed by ramps rather than stairs |
—
|
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: upper floors accessed by ramps rather than stairs | Statement: [Hawa Mahal, floorAccess, upper floors accessed by ramps rather than stairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floorAccess Context triple: [Hawa Mahal, floorAccess, upper floors accessed by ramps rather than stairs]
-
A.
floorAbove
Indicates that one floor is located directly above another floor in a vertical arrangement.
-
B.
floorCount
Indicates the number of floors or levels that a building or structure has.
-
C.
floor
Indicates that one entity is located on or forms the walking surface (the floor) beneath another entity within a space.
-
D.
hasFloor
Indicates that one entity possesses, includes, or is associated with a particular floor or level within a structure.
-
E.
hasLowerFloor
Indicates that one location, structure, or level includes or is directly connected to a floor situated below another floor.
- F. None of above. chosen
Provenance (4 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9ef2fe0819082bbe746ca682a7e |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd891bcd481909af5340a64ff69f9 |
completed | March 7, 2026, 7:49 a.m. |
Created at: March 6, 2026, 9:54 p.m.