Triple
T9027573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cell Broadband Engine |
E216085
|
entity |
| Predicate | vectorProcessing |
P85949
|
FINISHED |
| Object | supported |
—
|
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: supported | Statement: [Cell Broadband Engine, vectorProcessing, supported]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vectorProcessing Context triple: [Cell Broadband Engine, vectorProcessing, supported]
-
A.
vector
Indicates that one entity is a vector associated with, representing, or characterizing another entity (such as a quantity with magnitude and direction, or a carrier/representative of something).
-
B.
vectorLength
Indicates the numerical magnitude or size of a vector, typically computed from its components.
-
C.
hasVector
Indicates that an entity is associated with, or can be represented by, a specific vector in some vector space.
-
D.
computationInput
Indicates that an entity serves as input data or parameters consumed by a computation or processing activity.
-
E.
dimensionVector
Indicates a vector that specifies the magnitudes or extents of an entity along multiple dimensions or measurement axes.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7fcb308190af90d6be8700e498 |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 7:07 p.m.