Triple
T12573529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradesi Synagogue |
E295661
|
entity |
| Predicate | floorFeature |
P50429
|
FINISHED |
| Object | each Chinese tile has a unique design |
—
|
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: each Chinese tile has a unique design | Statement: [Paradesi Synagogue, floorFeature, each Chinese tile has a unique design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floorFeature Context triple: [Paradesi Synagogue, floorFeature, each Chinese tile has a unique design]
-
A.
floorCharacteristic
chosen
Indicates that a specified characteristic or property is attributed to a floor or flooring surface.
-
B.
floorType
Indicates the type or material classification of a floor associated with an entity.
-
C.
floorConfiguration
Indicates how the layout, structure, or arrangement of floors or levels is organized or configured in relation to one another.
-
D.
floor
Indicates that one entity is located on or forms the walking surface (the floor) beneath another entity within a space.
-
E.
floorBelow
Indicates that one entity is located on the floor directly beneath another entity within the same structure.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9550d84908190aea0f50055f6d92e |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95414692881909c52a1de7d224b44 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 11:50 p.m.