Triple
T1936827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AltiVec |
E41460
|
entity |
| Predicate | dataTypes |
P33715
|
FINISHED |
| Object | 16 8-bit integers per vector |
—
|
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: 16 8-bit integers per vector | Statement: [AltiVec, dataTypes, 16 8-bit integers per vector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTypes Context triple: [AltiVec, dataTypes, 16 8-bit integers per vector]
-
A.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
B.
dataTypeCollected
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
C.
storesDataType
Indicates that an entity is designed to hold, manage, or persist information of a specified data type.
-
D.
dataBusType
Indicates the type or category of data bus used to transfer data between components or systems.
-
E.
dataModel
Indicates a relationship where an entity defines, uses, or is structured according to a specific data model or schema.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2c5f6e481909b2d95861e2098f9 |
completed | March 7, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69abaff07cf88190b4883c5f17f90abd |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb25ef0ec8190b907963e9db0fe04 |
completed | March 7, 2026, 5:06 a.m. |
Created at: March 4, 2026, 7:36 p.m.