Triple
T23105109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legislative Assembly Hall, Puducherry |
E576138
|
entity |
| Predicate | buildingUseCategory |
P1844
|
FINISHED |
| Object | civic 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: civic building | Statement: [Legislative Assembly Hall, Puducherry, buildingUseCategory, civic building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingUseCategory Context triple: [Legislative Assembly Hall, Puducherry, buildingUseCategory, civic building]
-
A.
buildingType
chosen
Indicates the specific category or function that characterizes what kind of building something is.
-
B.
listedBuildingCategory
Indicates the heritage protection grade or category assigned to a building that is officially recognized as a listed structure.
-
C.
currentBuildingUse
Indicates the present functional purpose or activity for which a building is being used.
-
D.
buildingUsedBy
Indicates that a particular building is utilized or occupied by a specified entity for some purpose.
-
E.
typeOfBuildingSpace
Indicates the specific kind or category of building space that an entity represents or occupies.
- 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_69e245f4af548190898d434a64a1e774 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e0ad44c81908e1873d4b3860323 |
completed | April 29, 2026, 4:50 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:58 p.m.