Triple
T27654516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lower chapel of Sainte-Chapelle |
E696954
|
entity |
| Predicate | floorAreaRelation |
P163935
|
FINISHED |
| Object | smaller than the upper chapel |
—
|
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: smaller than the upper chapel | Statement: [lower chapel of Sainte-Chapelle, floorAreaRelation, smaller than the upper chapel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floorAreaRelation Context triple: [lower chapel of Sainte-Chapelle, floorAreaRelation, smaller than the upper chapel]
-
A.
floorAreaFeature
Indicates a relationship where a specific feature or characteristic is associated with the floor area of an entity or space.
-
B.
floorPlanRelation
Indicates a spatial or structural relationship between elements as defined within a building’s floor plan layout.
-
C.
hasFloorArea
Indicates that an entity possesses a specified amount of floor space as a measurable area.
-
D.
roofArea
Indicates the total surface area covered by the roof of a structure.
-
E.
floorAreaRank
Indicates the relative ordering of entities based on the size of their floor area, with lower ranks representing larger floor areas.
- F. None of above. chosen
Provenance (4 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 2:33 p.m.