Triple
T19352421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPU |
E484054
|
entity |
| Predicate | canBeType |
P14124
|
FINISHED |
| Object | microprocessor |
—
|
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: microprocessor | Statement: [CPU, canBeType, microprocessor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeType Context triple: [CPU, canBeType, microprocessor]
-
A.
canBeTypeOf
chosen
Indicates that one entity is capable of serving as, or being classified as, a particular type or category of another entity.
-
B.
canBeDefinedFor
Indicates that a certain concept, operation, or property is applicable to and can be meaningfully specified for a given entity or set of entities.
-
C.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
canBeAdaptedBy
Indicates that one entity is capable of being modified, adjusted, or tailored for use by another entity.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61905b16881909ab0e932bb9a0cda |
completed | April 20, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e4dd13a8cc81909cd02668564c9f29 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.