Triple
T13493690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foxton Locks |
E320704
|
entity |
| Predicate | lockConfiguration |
P110623
|
FINISHED |
| Object | staircase |
—
|
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: staircase | Statement: [Foxton Locks, lockConfiguration, staircase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lockConfiguration Context triple: [Foxton Locks, lockConfiguration, staircase]
-
A.
lockType
Indicates the specific kind or category of locking mechanism or access restriction applied to an entity or resource.
-
B.
lockSystemSupplied
Indicates that a system-provided locking mechanism is used to control access or state, rather than a custom or user-defined lock.
-
C.
lockBehavior
Indicates how an entity controls or restricts access, modification, or interaction with another entity through locking rules or mechanisms.
-
D.
unlockBehavior
Indicates that one entity enables access to or activates the behavior, functionality, or state of another entity.
-
E.
lockedMeans
Indicates that one state, condition, or action guarantees or necessitates another, such that when the first is "locked in," the second must follow.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf4da2c88190a867b53529d39545 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:43 p.m.