Triple
T27754656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ArchiMate |
E701304
|
entity |
| Predicate | hasViewpointConcept |
P173366
|
FINISHED |
| Object | viewpoint |
—
|
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: viewpoint | Statement: [ArchiMate, hasViewpointConcept, viewpoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewpointConcept Context triple: [ArchiMate, hasViewpointConcept, viewpoint]
-
A.
hasViewpointType
Indicates that something is associated with or characterized by a particular type or category of viewpoint or perspective.
-
B.
hasViewpointStatus
Indicates that an entity holds a particular evaluative or perspectival status (e.g., stance, opinion, or viewpoint classification) with respect to something.
-
C.
hasViewingPointFor
Indicates that one entity serves as a vantage point or location from which another entity can be viewed or observed.
-
D.
isMajorViewpointOf
Indicates that a particular perspective, opinion, or interpretation is a primary or widely recognized way of viewing or understanding something.
-
E.
hasMajorViewpoint
Indicates that an entity holds, expresses, or is characterized by a primary or dominant perspective, opinion, or stance on a subject.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 27, 2026, 4:22 p.m.