Triple
T9577046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bharat Mata Mandir |
E231070
|
entity |
| Predicate | hasFloorDedicatedTo |
P68010
|
FINISHED |
| Object | Hindu deities |
—
|
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: Hindu deities | Statement: [Bharat Mata Mandir, hasFloorDedicatedTo, Hindu deities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloorDedicatedTo Context triple: [Bharat Mata Mandir, hasFloorDedicatedTo, Hindu deities]
-
A.
hasFloor
Indicates that one entity possesses, includes, or is associated with a particular floor or level within a structure.
-
B.
hasFloorUse
chosen
Indicates that a particular floor or level of a building is designated for a specific function, activity, or type of use.
-
C.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
-
D.
hasUpperFloorUse
Indicates that an entity’s upper floor is assigned or designated for a particular use or function.
-
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.
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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99ad7d108190a0b8c975351ea727 |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:05 p.m.