Triple
T29247016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zorro II |
E741465
|
entity |
| Predicate | supportsDMA |
P204063
|
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: [Zorro II, supportsDMA, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDMA Context triple: [Zorro II, supportsDMA, yes]
-
A.
DMA
Indicates a relationship where one entity performs, manages, or is responsible for direct marketing activities toward another entity.
-
B.
supportsPCM
Indicates that one entity is capable of handling, processing, or is compatible with PCM (Pulse-Code Modulation) audio data used by another entity.
-
C.
supportsBusSpeed
Indicates that one entity is capable of operating at, or is compatible with, a specified bus communication speed of another entity.
-
D.
supportsSymmetricMultiprocessing
Indicates that an entity provides or is compatible with symmetric multiprocessing, allowing multiple processors to share memory and workload equally.
-
E.
supportsDRAMRefresh
Indicates that one entity provides the capability or functionality needed to perform DRAM refresh operations for another entity.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a0316136a14819085bb88563d5abc42 |
completed | May 12, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_6a03158a962c81909f17d58197f6ba00 |
completed | May 12, 2026, 11:56 a.m. |
| PDg | Predicate description generation | batch_6a0316129c9081908f01528f62fe8997 |
completed | May 12, 2026, 11:59 a.m. |
Created at: April 28, 2026, 12:33 p.m.