Triple
T24657850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort of Fenestrelle |
E610443
|
entity |
| Predicate | staircaseLength |
P1275
|
FINISHED |
| Object | over 4,000 steps |
—
|
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: over 4,000 steps | Statement: [Fort of Fenestrelle, staircaseLength, over 4,000 steps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: staircaseLength Context triple: [Fort of Fenestrelle, staircaseLength, over 4,000 steps]
-
A.
numberOfStairs
chosen
Indicates the quantity of stairs associated with or present in a given context or structure.
-
B.
numberOfStaircases
Indicates the quantity of distinct staircases associated with or present in a given entity or location.
-
C.
hasStairway
Indicates that one entity includes or is connected to another entity by a stairway providing vertical access between levels.
-
D.
hasStaircaseType
Indicates the specific type or design classification of a staircase associated with an entity.
-
E.
hasStairFunction
Indicates that one entity serves as a stair-related functional feature (e.g., providing access via stairs) for another 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:34 a.m.