Triple
T35774858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B7900 |
E1034261
|
entity |
| Predicate | hasComputingDomain |
P206044
|
FINISHED |
| Object | business computing |
—
|
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 computing | Statement: [B7900, hasComputingDomain, business computing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComputingDomain Context triple: [B7900, hasComputingDomain, business computing]
-
A.
hasCollaborationDomain
Indicates that two or more entities work together within a specified field, area, or domain of collaboration.
-
B.
hasCommunicationDomain
Indicates that one entity operates, functions, or is relevant within a specified communication-related domain or area.
-
C.
hasDomainFeature
Indicates that something possesses or is characterized by a specific feature or attribute within a particular domain or context.
-
D.
hasServiceDomain
Indicates that an entity operates within, is associated with, or is responsible for a particular service domain or area of service.
-
E.
hasConvergenceDomain
Indicates the domain or set of conditions under which a given process, function, or sequence converges.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.