Triple
T18850159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pombaline cage |
E461017
|
entity |
| Predicate | typicalLocationInBuilding |
P94409
|
FINISHED |
| Object | interior walls and floors |
—
|
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: interior walls and floors | Statement: [Pombaline cage, typicalLocationInBuilding, interior walls and floors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLocationInBuilding Context triple: [Pombaline cage, typicalLocationInBuilding, interior walls and floors]
-
A.
locatedInBuildingUsedAs
Indicates that something is located inside a building that is being used for a specified purpose or function.
-
B.
locatedInBuildingWithFeature
Indicates that something is located in a building that possesses a specified feature or characteristic.
-
C.
locatedOnBuilding
Indicates that one entity is physically situated on the exterior or rooftop surface of a building.
-
D.
locatedInSectionOfBuilding
chosen
Indicates that one entity is situated within a specific section or area of a building.
-
E.
seatBuildingLocatedIn
Indicates that the building serving as a seat (e.g., headquarters or main office) is geographically located within a specified area or place.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8f27cf481908c60fcdce412a224 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.