Triple
T29390113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SD memory card |
E745349
|
entity |
| Predicate | supportsWriteProtection |
P168658
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [SD memory card, supportsWriteProtection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsWriteProtection Context triple: [SD memory card, supportsWriteProtection, yes]
-
A.
hasWriteProtection
chosen
Indicates that an entity is configured to prevent writing or modification operations.
-
B.
supportsROMBlocks
Indicates that one entity provides compatibility with or the capability to use ROM (Read-Only Memory) blocks associated with another entity.
-
C.
hasLandscapeProtection
Indicates that an area or object is subject to legal or formal measures aimed at preserving its landscape or scenic character.
-
D.
dataProtectionFeature
Indicates a feature or mechanism designed to safeguard data from unauthorized access, alteration, loss, or misuse.
-
E.
supportsMemoryProtection
Indicates that one entity provides mechanisms to prevent unauthorized access or interference with another entity’s memory space.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a033d975d788190aafc4be10d6c5c1c |
completed | May 12, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_6a033cc2668481908cb696e57632a68f |
completed | May 12, 2026, 2:44 p.m. |
Created at: April 28, 2026, 2:41 p.m.