Triple
T1840293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pedro Miguel Locks |
E41161
|
entity |
| Predicate | lockType |
P34001
|
FINISHED |
| Object | gravity-fed lock |
—
|
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: gravity-fed lock | Statement: [Pedro Miguel Locks, lockType, gravity-fed lock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lockType Context triple: [Pedro Miguel Locks, lockType, gravity-fed lock]
-
A.
keyType
Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
-
B.
regionLocking
Indicates that access to or use of something is restricted based on the geographic region of the user or device.
-
C.
tidalLock
Indicates that one astronomical body always shows the same face to another because its rotational period matches its orbital period around that body.
-
D.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
-
E.
restraintType
Indicates the specific kind or method of restraint applied in a given situation or relationship.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafd88ebc81908208394746351fe6 |
completed | March 7, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69abb32a8d548190a231c7c2ce276a5e |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:33 p.m.