Triple
T27754544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TOGAF |
E701302
|
entity |
| Predicate | ADMPhase |
P22825
|
FINISHED |
| Object | Business Architecture |
—
|
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: Business Architecture | Statement: [TOGAF, ADMPhase, Business Architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ADMPhase Context triple: [TOGAF, ADMPhase, Business Architecture]
-
A.
applicationPhase
Indicates the specific stage or step an application is currently in within a broader application process.
-
B.
programPhase
chosen
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
C.
commissionedPhase
Indicates that an entity has formally initiated or authorized a particular phase or stage of a project, process, or work.
-
D.
majorPhase
Indicates that one phase is a primary or dominant stage within a larger process, lifecycle, or sequence.
-
E.
acquisitionPhase
Indicates the stage or phase within an overall acquisition process in which the related entities are currently involved.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 4:22 p.m.