Triple
T27055870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | enterprise application architecture |
E684894
|
entity |
| Predicate | typicallyInvolvesRole |
P18942
|
FINISHED |
| Object | enterprise architect |
—
|
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: enterprise architect | Statement: [enterprise application architecture, typicallyInvolvesRole, enterprise architect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyInvolvesRole Context triple: [enterprise application architecture, typicallyInvolvesRole, enterprise architect]
-
A.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
B.
involvesPartyRole
Indicates that a situation, event, or agreement includes a participant fulfilling a specific role or function within that context.
-
C.
typicalRole
chosen
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
D.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
E.
roleInActs
Indicates the specific function or character that an entity performs or portrays within one or more acts or performances.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69ff65987ff88190b09be64f7c0e1da9 |
completed | May 9, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69ff6525b0548190bef7a9f009e00bb8 |
completed | May 9, 2026, 4:47 p.m. |
Created at: April 27, 2026, 8:17 a.m.