Triple
T33008326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rampuri knife |
E844570
|
entity |
| Predicate | hasFoldingLock |
P194529
|
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: [Rampuri knife, hasFoldingLock, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFoldingLock Context triple: [Rampuri knife, hasFoldingLock, true]
-
A.
hasLock
Indicates that one entity possesses or is secured by a lock associated with another entity.
-
B.
hasLockOperation
Indicates that an entity is associated with a specific lock-related operation, such as locking, unlocking, or otherwise controlling access.
-
C.
foldingType
Indicates the specific manner or configuration in which something is folded or arranged into a folded form.
-
D.
canFold
Indicates that one entity has the ability to be bent or collapsed into a more compact form, typically without breaking.
-
E.
canBeLocked
Indicates that an entity has the capability to be secured or made inaccessible by applying a lock or locking mechanism.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
| PDg | Predicate description generation | batch_69fd783e9e5c819087dec7fefa03700d |
completed | May 8, 2026, 5:44 a.m. |
Created at: May 1, 2026, 1:23 a.m.