Triple
T14388643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARMv7-A |
E356786
|
entity |
| Predicate | architectureProfile |
P114052
|
FINISHED |
| Object | Application profile |
—
|
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: Application profile | Statement: [ARMv7-A, architectureProfile, Application profile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architectureProfile Context triple: [ARMv7-A, architectureProfile, Application profile]
-
A.
architectureName
Indicates the specific name or title assigned to an architecture.
-
B.
architectureAssociated
Indicates that there is a relationship or connection between an entity and a particular architectural style, feature, or practice.
-
C.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
D.
architecturalPlanner
Indicates a relationship where an entity is responsible for designing, organizing, or planning the architectural structure or layout of another entity.
-
E.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90283b9c8190b50d30ad58bfe085 |
completed | April 14, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e08b6c08190bb4c929deab236a6 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:16 a.m.