Triple
T32496538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shiv Niwas |
E830538
|
entity |
| Predicate | functionWithinComplex |
P46874
|
FINISHED |
| Object | residential or guest wing |
—
|
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: residential or guest wing | Statement: [Shiv Niwas, functionWithinComplex, residential or guest wing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionWithinComplex Context triple: [Shiv Niwas, functionWithinComplex, residential or guest wing]
-
A.
hasFunctionInComplex
chosen
Indicates that an entity performs a specific functional role within a larger molecular or structural complex.
-
B.
positionWithinComplex
Indicates that one entity is located inside or forms a component part of a larger complex or compound structure.
-
C.
isWithinStructure
Indicates that one entity is located inside the physical or logical boundaries of another structure.
-
D.
functionWithinSite
Indicates that one function or activity occurs or is carried out within the spatial or organizational bounds of a particular site.
-
E.
hasComplex
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 12:59 a.m.