Triple
T23294436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillmorton Locks |
E590124
|
entity |
| Predicate | hasParallelLocks |
P151736
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hillmorton Locks, hasParallelLocks, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParallelLocks Context triple: [Hillmorton Locks, hasParallelLocks, true]
-
A.
hasParallelIn
Indicates that one entity has a corresponding or analogous counterpart in another context, system, or domain.
-
B.
hasParallelImplementation
Indicates that one implementation of a function, process, or algorithm has a corresponding version designed to run in parallel.
-
C.
hasLocksAt
Indicates that one entity possesses or provides locks that are located at or associated with a specific place or position of another entity.
-
D.
hasNumberOfLocks
Indicates the quantity of locks that an entity possesses or is equipped with.
-
E.
hasConcurrency
Indicates that two or more processes, tasks, or operations can occur or be executed simultaneously or with overlapping time intervals.
- 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196cdce7081908ca1cf9107b87f61 |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:02 p.m.