Triple
T28582973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARM Cortex-A |
E723425
|
entity |
| Predicate | includesArchitecture |
P24956
|
FINISHED |
| Object | ARMv7-A |
—
|
NE NERFINISHED |
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: ARMv7-A | Statement: [ARM Cortex-A, includesArchitecture, ARMv7-A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesArchitecture Context triple: [ARM Cortex-A, includesArchitecture, ARMv7-A]
-
A.
usesArchitecture
chosen
Indicates that one entity is built, implemented, or operates according to the architectural style, framework, or design specified by another entity.
-
B.
usesArchitectureComponent
Indicates that one entity employs or incorporates a specific architecture component as part of its structure, design, or implementation.
-
C.
hasArchitectureBy
Indicates that an entity’s architectural design was created or authored by a specified architect or architectural firm.
-
D.
toArchitecture
Indicates a relationship in which something is designed, structured, or organized according to a particular architectural style, plan, or system.
-
E.
exampleArchitecture
Indicates that one entity serves as a representative or illustrative instance of the architectural style, structure, or design of 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: April 28, 2026, 4:16 a.m.