Triple
T29233251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roysambu |
E741126
|
entity |
| Predicate | commonBuildingType |
P1844
|
FINISHED |
| Object | multi-storey residential buildings |
—
|
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: multi-storey residential buildings | Statement: [Roysambu, commonBuildingType, multi-storey residential buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonBuildingType Context triple: [Roysambu, commonBuildingType, multi-storey residential buildings]
-
A.
buildingType
chosen
Indicates the specific category or function that characterizes what kind of building something is.
-
B.
buildingTypeServed
Indicates the type of building that is served, supported, or catered to by a given entity or system.
-
C.
publicBuilding
Indicates that a building is designated for public use or access, typically serving communal, governmental, or civic functions.
-
D.
buildingTypeAtCenter
Indicates that a specific type of building is located at the central position of a given area or spatial context.
-
E.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 28, 2026, 12:28 p.m.