Triple
T27227762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lock 43 |
E682062
|
entity |
| Predicate | lockNumber |
P73976
|
FINISHED |
| Object | 43 |
—
|
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: 43 | Statement: [Lock 43, lockNumber, 43]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lockNumber Context triple: [Lock 43, lockNumber, 43]
-
A.
lockName
Indicates that an entity has or is associated with a specific lock identifier or name used to distinguish it from other locks.
-
B.
lockType
Indicates the specific kind or category of locking mechanism or access restriction applied to an entity or resource.
-
C.
lock
Indicates that an entity secures or fastens another entity so that it cannot be opened, accessed, or changed without authorization.
-
D.
lockFile
Indicates that a file is being restricted or secured to prevent access or modification by others.
-
E.
hasLockNumber
chosen
Indicates that an entity is associated with a specific lock identified by a number.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6264bcdc08190b0860b3015aac6c6 |
completed | May 2, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:45 a.m.